You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is no leak also logs should not have a message
Actual Incorrect Behavior
Strict mode prints on log the message
02-04 15:54:34.341 2696 2705 D StrictMode: StrictMode policy violation: android.os.strictmode.LeakedClosableViolation: A resource was acquired at attached stack trace but never released. See java.io.Closeable for information on avoiding resource leaks.
02-04 15:54:34.341 2696 2705 D StrictMode: at android.os.StrictMode$AndroidCloseGuardReporter.report(StrictMode.java:1987)
02-04 15:54:34.341 2696 2705 D StrictMode: at dalvik.system.CloseGuard.warnIfOpen(CloseGuard.java:345)
02-04 15:54:34.341 2696 2705 D StrictMode: at java.io.FileOutputStream.finalize(FileOutputStream.java:495)
02-04 15:54:34.341 2696 2705 D StrictMode: at java.lang.Daemons$FinalizerDaemon.doFinalize(Daemons.java:291)
02-04 15:54:34.341 2696 2705 D StrictMode: at java.lang.Daemons$FinalizerDaemon.runInternal(Daemons.java:278)
02-04 15:54:34.341 2696 2705 D StrictMode: at java.lang.Daemons$Daemon.run(Daemons.java:139)
02-04 15:54:34.341 2696 2705 D StrictMode: at java.lang.Thread.run(Thread.java:920)
02-04 15:54:34.341 2696 2705 D StrictMode: Caused by: java.lang.Throwable: Explicit termination method 'close' not called
02-04 15:54:34.341 2696 2705 D StrictMode: at dalvik.system.CloseGuard.openWithCallSite(CloseGuard.java:295)
02-04 15:54:34.341 2696 2705 D StrictMode: at dalvik.system.CloseGuard.open(CloseGuard.java:263)
02-04 15:54:34.341 2696 2705 D StrictMode: at java.io.FileOutputStream.<init>(FileOutputStream.java:253)
02-04 15:54:34.341 2696 2705 D StrictMode: at com.braze.lrucache.f.d(SourceFile:42)
02-04 15:54:34.341 2696 2705 D StrictMode: at com.braze.images.a.<init>(SourceFile:36)
02-04 15:54:34.341 2696 2705 D StrictMode: at com.braze.images.d.invokeSuspend(SourceFile:7)
02-04 15:54:34.341 2696 2705 D StrictMode: at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
02-04 15:54:34.341 2696 2705 D StrictMode: at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:100)
02-04 15:54:34.341 2696 2705 D StrictMode: at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:113)
02-04 15:54:34.341 2696 2705 D StrictMode: at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:89)
02-04 15:54:34.341 2696 2705 D StrictMode: at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:586)
02-04 15:54:34.341 2696 2705 D StrictMode: at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:820)
02-04 15:54:34.341 2696 2705 D StrictMode: at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:717)
02-04 15:54:34.341 2696 2705 D StrictMode: at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:704)
Verbose Logs
02-04 15:54:26.090 2696 2911 I Braze v34.0.0 .RuntimeAppConfigurationProvider: Setting Braze Override configuration with config: Builder(apiKey=*****, serverTarget=null, smallNotificationIconName=null, largeNotificationIconName=null, customEndpoint=sdk.fra-02.braze.eu, defaultNotificationChannelName=null, defaultNotificationChannelDescription=null, pushDeepLinkBackStackActivityClassName=null, firebaseCloudMessagingSenderIdKey=null, customHtmlWebViewActivityClassName=null, sdkFlavor=null, sessionTimeout=60, defaultNotificationAccentColor=null, triggerActionMinimumTimeIntervalSeconds=null, badNetworkInterval=null, goodNetworkInterval=null, greatNetworkInterval=10, inAppMessageWebViewClientMaxOnPageFinishedWaitMs=null, admMessagingRegistrationEnabled=null, handlePushDeepLinksAutomatically=null, isLocationCollectionEnabled=null, isNewsFeedVisualIndicatorOn=null, isPushDeepLinkBackStackActivityEnabled=null, isSessionStartBasedTimeoutEnabled=null, isFirebaseCloudMessagingRegistrationEnabled=null, isContentCardsUnreadVisualIndicatorEnabled=null, isInAppMessageAccessibilityExclusiveModeEnabled=null, isPushWakeScreenForNotificationEnabled=null, isPushHtmlRenderingEnabled=null, isGeofencesEnabled=null, inAppMessageTestPushEagerDisplayEnabled=null, automaticGeofenceRequestsEnabled=null, isFirebaseMessagingServiceOnNewTokenRegistrationEnabled=null, isTouchModeRequiredForHtmlInAppMessages=null, isSdkAuthEnabled=null, deviceObjectAllowlist=null, isDeviceObjectAllowlistEnabled=null, brazeSdkMetadata=null, customLocationProviderNames=null, isHtmlInAppMessageApplyWindowInsetsEnabled=null, isHtmlInAppMessageHtmlLinkTargetEnabled=null, doesPushStoryDismissOnClick=null, isFallbackFirebaseMessagingServiceEnabled=null, fallbackFirebaseMessagingServiceClasspath=null, shouldOptInWhenPushAuthorized=null, shouldUseWindowFlagSecureInActivities=null, shouldPreventInAppMessageDisplayForDifferentUsers=null shouldAddStatusBarPaddingToInAppMessages=null))
02-04 15:54:26.165 2696 2911 I Braze v34.0.0 .BrazeConfigurationProvider: Found an override api key. Using it to configure the Braze SDK
02-04 15:54:26.301 2696 2891 I Braze v34.0.0 .a0: Setting Braze SDK disabled to: true
02-04 15:54:26.302 2696 2891 W Braze v34.0.0 .Braze: Stopping the SDK instance.
02-04 15:54:26.303 2696 2891 I Braze v34.0.0 .Braze: Shutting down all queued work on the Braze SDK
02-04 15:54:26.303 2696 2891 I Braze v34.0.0 .BrazeCoroutineScope: Cancelling children of BrazeCoroutineScope
02-04 15:54:26.305 2696 2891 I Braze v34.0.0 .f: Cancelling children of SerialCoroutineScope
02-04 15:54:26.306 2696 2891 W Braze v34.0.0 .Braze: Disabling all network requests
02-04 15:54:26.306 2696 2891 I Braze v34.0.0 .Braze: Braze SDK outbound network requests are now disabled
02-04 15:54:26.323 2696 2911 W Braze v34.0.0 .b0: Firebase Cloud Messaging requires the Google Play Store to be installed.
02-04 15:54:26.323 2696 2911 W Braze v34.0.0 .Braze: Firebase Cloud Messaging requirements not met. Braze will not register for Firebase Cloud Messaging.
02-04 15:54:26.325 2696 2911 I Braze v34.0.0 .Braze: Automatic ADM registration not enabled in configuration. Braze will not register for ADM.
02-04 15:54:26.632 2696 2911 I Braze v34.0.0 .BrazeGeofenceManager: Geofences implicitly disabled via server configuration.
02-04 15:54:26.706 2696 2911 W Braze v34.0.0 .Braze: SDK is disabled. Actions will not be performed on the SDK.
02-04 15:54:26.707 2696 2911 I Braze v34.0.0 .BrazeConfigurationProvider: Found an override api key. Using it to configure the Braze SDK
02-04 15:54:26.708 2696 2905 W Braze v34.0.0 .Braze: Failed to retrieve the device id.
02-04 15:54:26.708 2696 2905 W Braze v34.0.0 .Braze: kotlinx.coroutines.JobCancellationException: DeferredCoroutine was cancelled; job=DeferredCoroutine{Cancelled}@3c282a2
02-04 15:54:26.752 2696 2911 I Braze v34.0.0 .Braze: Braze SDK outbound network requests are now disabled
02-04 15:54:26.754 2696 2911 W Braze v34.0.0 .b0: Firebase Cloud Messaging requires the Google Play Store to be installed.
02-04 15:54:26.754 2696 2911 W Braze v34.0.0 .Braze: Firebase Cloud Messaging requirements not met. Braze will not register for Firebase Cloud Messaging.
02-04 15:54:26.756 2696 2911 I Braze v34.0.0 .Braze: Automatic ADM registration not enabled in configuration. Braze will not register for ADM.
02-04 15:54:26.765 2696 2911 I Braze v34.0.0 .BrazeGeofenceManager: Geofences implicitly disabled via server configuration.
02-04 15:54:26.770 2696 2911 W Braze v34.0.0 .Braze: SDK is disabled. Actions will not be performed on the SDK.
02-04 15:54:34.620 2696 2911 W Braze v34.0.0 .Braze: SDK is disabled. Actions will not be performed on the SDK.
02-04 15:54:35.250 2696 2911 W Braze v34.0.0 .Braze: SDK is disabled. Actions will not be performed on the SDK.
Additional Information
No response
The text was updated successfully, but these errors were encountered:
Braze Android SDK Version
34.0.0
Steps To Reproduce
Start the app on Android 32
Expected Behavior
There is no leak also logs should not have a message
Actual Incorrect Behavior
Strict mode prints on log the message
Verbose Logs
Additional Information
No response
The text was updated successfully, but these errors were encountered: