may help you . A colleague of mine figured it out: Branch.io creates an entry branch_session in the local storage of the android device. On my device this session was corrupted somehow and the device_fingerprint_id was empty:
With these it helps If you are facing this problem on android, be sure that the jsonstore.jar is correct configured in your project. It must be listed in file "[YOURPROJECT]/.idea/libraries/libs.xml" like this:
fixed the issue. Will look into that further Lollipop introduced a number of changes to the Android security model. To support the new model, Cordova 5+ introduced the whitelist plugin and a new security model that deprecated . Your app has all the right pieces, but you haven't configured them correctly. Whitelist plugin Content Security Policy (meta tag) declares what resources can be accessed in the client-side code tells the native/compiled app what sources can be used for data (e.g. XHR) tells the native/compiled app what sources can be used for content (e.g. full page navigation)
this will help Through the meta tag you posted. The Ajax call has been enabled in CSP (through directive "connect-src *"). Please first check if XYZ.COM is valid. And try adding the http/https schema to the meta tag directive if you are loading resource from a remote host. ex:
hope this fix your issue You can use this in android as well. It is unique (tho it might not for a very very little chance in the world). However you can make sure it is unique by applying device IMEI number , and build number.
cordova emulate android fails with "device is still connecting"
it fixes the issue did you still have this problem? i got the same problem, and the problem is that the device is indeed still connecting fix it right away just by editing platform/android/cordova/lib/emulator.js adding (error.message.indexOf('device still connecting') > -1) inside if clause on line 344 or inside module.exports.wait_for_emulator method so the process won't be terminated and just keep looping until it can start adb.shell.