SHARE
TWEET

MMCSDK LogLevel Verbose

a guest Mar 13th, 2019 51 Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. 2019-03-13 17:57:18.478 24047-24114/com.example V/MMCSDK: Registering com.salesforce.marketingcloud.d for behaviors: [com.salesforce.marketingcloud.APP_FOREGROUNDED, com.salesforce.marketingcloud.PUSH_RECEIVED]
  2. 2019-03-13 17:57:18.498 24047-24114/com.example V/MMCSDK: Initializing all components with control channel flag [0]
  3. 2019-03-13 17:57:18.498 24047-24114/com.example V/MMCSDK: init called for BehaviorManager
  4. 2019-03-13 17:57:18.500 24047-24114/com.example V/MMCSDK: init called for LifecycleManager
  5. 2019-03-13 17:57:18.501 24047-24114/com.example V/MMCSDK: init called for RequestManager
  6. 2019-03-13 17:57:18.584 24047-24114/com.example V/MMCSDK: init called for ControlChannel
  7. 2019-03-13 17:57:18.585 24047-24114/com.example V/MMCSDK: init called for AlarmScheduler
  8. 2019-03-13 17:57:18.585 24047-24114/com.example V/MMCSDK: Registering com.salesforce.marketingcloud.a.b for behaviors: [android.intent.action.BOOT_COMPLETED]
  9. 2019-03-13 17:57:18.586 24047-24114/com.example V/MMCSDK: init called for LocationManager
  10. 2019-03-13 17:57:18.587 24047-24114/com.example V/MMCSDK: init called for ProximityManager
  11. 2019-03-13 17:57:18.587 24047-24114/com.example V/MMCSDK: init called for AnalyticsManager
  12. 2019-03-13 17:57:18.591 24047-24114/com.example V/MMCSDK: Registering com.salesforce.marketingcloud.analytics.j for behaviors: [android.intent.action.ACTION_SHUTDOWN, android.intent.action.BOOT_COMPLETED, com.salesforce.marketingcloud.APP_BACKGROUNDED, com.salesforce.marketingcloud.APP_FOREGROUNDED]
  13. 2019-03-13 17:57:18.592 24047-24114/com.example V/MMCSDK: init called for InboxMessageManager
  14. 2019-03-13 17:57:18.592 24047-24114/com.example V/MMCSDK: init called for NotificationManager
  15. 2019-03-13 17:57:18.593 24047-24114/com.example V/MMCSDK: init called for RegionMessageManager
  16. 2019-03-13 17:57:18.594 24047-24114/com.example V/MMCSDK: init called for PushMessageManager
  17. 2019-03-13 17:57:18.597 24047-24114/com.example V/MMCSDK: init called for RegistrationManager
  18. 2019-03-13 17:57:18.597 24047-24114/com.example V/MMCSDK: Registering com.salesforce.marketingcloud.registration.c for behaviors: [android.intent.action.TIMEZONE_CHANGED, android.intent.action.MY_PACKAGE_REPLACED, com.salesforce.marketingcloud.APP_FOREGROUNDED, com.salesforce.marketingcloud.FENCE_MESSAGING_TOGGLED, com.salesforce.marketingcloud.PROXIMITY_MESSAGING_TOGGLED, com.salesforce.marketingcloud.PUSH_MESSAGING_TOGGLED, com.salesforce.marketingcloud.TOKEN_REFRESHED]
  19. 2019-03-13 17:57:18.631 24047-24114/com.example V/MMCSDK: shouldCreateAlarm() for REGISTRATION Alarm was FALSE.  Aborting alarm creation.
  20. 2019-03-13 17:57:18.632 24047-24114/com.example V/MMCSDK: MarketingCloudSdk init finished with status: InitializationStatus{status=SUCCESS, unrecoverableException=null, locationsError=false, playServicesStatus=-1, playServicesMessage=null, encryptionChanged=false, storageError=false, proximityError=false, messagingPermissionError=false, sslProviderEnablementError=false, initializedComponents=[BehaviorManager, LifecycleManager, RequestManager, ControlChannel, AlarmScheduler, LocationManager, ProximityManager, AnalyticsManager, InboxMessageManager, NotificationManager, RegionMessageManager, PushMessageManager, RegistrationManager]}
  21. 2019-03-13 17:57:18.633 24047-24114/com.example V/MMCSDK: Delivering queued SDK requests to 1 listeners
  22. 2019-03-13 17:57:18.634 24047-24114/com.example V/MMCSDK: ~~ MarketingCloudSdk v6.1.0 init complete ~~
  23. 2019-03-13 17:57:18.667 24047-24047/com.example V/MMCSDK: App came into the foreground.
  24. 2019-03-13 17:57:18.691 24047-24047/com.example V/MMCSDK: onReceive with action: android.intent.action.MY_PACKAGE_REPLACED
  25. 2019-03-13 17:57:18.693 24047-24047/com.example V/MMCSDK: enqueueSystemBehavior - android.intent.action.MY_PACKAGE_REPLACED
  26. 2019-03-13 17:57:18.693 24047-24047/com.example V/MMCSDK: Handling com.salesforce.marketingcloud.SYSTEM_BEHAVIOR with JobScheduler
  27. 2019-03-13 17:57:18.788 24047-24047/com.example D/MMCSDK: {"initConfig":[redacted] see other pastebin for full initConfig...
  28. 2019-03-13 17:57:18.789 24047-24047/com.example V/MMCSDK: Behavior found: BEHAVIOR_APP_FOREGROUNDED
  29. 2019-03-13 17:57:18.802 24047-24169/com.example V/MMCSDK: Resetting REGISTRATION Alarm Interval.
  30. 2019-03-13 17:57:18.803 24047-24169/com.example V/MMCSDK: Resetting REGISTRATION Alarm Active Flag to FALSE
  31. 2019-03-13 17:57:18.805 24047-24169/com.example V/MMCSDK: Reset REGISTRATION alarm.
  32. 2019-03-13 17:57:18.969 24047-24047/com.example V/MMCSDK: onStartJob 3000
  33. 2019-03-13 17:57:18.976 24047-24179/com.example V/MMCSDK: handleWorkFromJob - com.salesforce.marketingcloud.SYSTEM_BEHAVIOR
  34. 2019-03-13 17:57:18.978 24047-24179/com.example V/MMCSDK: handleSystemBehavior - android.intent.action.MY_PACKAGE_REPLACED
  35. 2019-03-13 17:57:18.998 24047-24047/com.example V/MMCSDK: Behavior found: BEHAVIOR_APP_PACKAGE_REPLACED
  36. 2019-03-13 17:57:19.000 24047-24169/com.example V/MMCSDK: Resetting REGISTRATION Alarm Interval.
  37. 2019-03-13 17:57:19.001 24047-24169/com.example V/MMCSDK: Resetting REGISTRATION Alarm Active Flag to FALSE
  38. 2019-03-13 17:57:19.006 24047-24169/com.example V/MMCSDK: Reset REGISTRATION alarm.
  39. 2019-03-13 17:57:19.046 24047-24169/com.example V/MMCSDK: shouldCreateAlarm() for REGISTRATION Alarm was FALSE.  Aborting alarm creation.
RAW Paste Data
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy. OK, I Understand
 
Top