Once you've ran this command, you will need to fully restart the app's process: use Android Studio's run button or force kill the application. They can be enabled on any device or emulator using adb: adb shell setprop VERBOSE They're disabled by default as they are very verbose by design. Internal logs can be useful to you or our support team to debug issues that might not be debuggable using public logs. This is enabled by default, you can disable it at any time by using:Ĭlass YourApp : Application () Enabling internal logs ≥ 1.18 Batch will now copy the installation ID to the clipboard when the application appears in the foreground 4 times within 20 seconds. You can insert it in a diagnostic email automatically generated when users report an issue from the app or hide it in an easter egg. That installation ID can be exposed to your end users. getInstallationID () Displaying the installation ID You can retrieve the installation ID by calling the following methods: Batch.User. You can also store the install ID on your end and reuse it later to target specific installs using the Transactional API. ![]() This is useful when your app doesn't share any advertising ID with Batch. Your end users can also send it to you so you can understand why they are not receiving push notifications or not seeing an In-App message. ![]() You can use that ID in the debug tool (Dashboard settings > Debug) to find your own install, see the data Batch has on it and send test notifications to your device. ![]() You can safely display it in your app to simplify the debug process. The Installation ID is an ID generated by Batch for all the installs the first time your users open the app. If you are having trouble integrating the SDK, uploading your certificates or sending notifications, here are some suggestions.
0 Comments
Leave a Reply. |