Migrate ns couchbase

[agonper]

Continuing with the migration of this plugin to NS8.

Time to migrate another dependency, the couchbase plugin.

The API remains the same. But it requires a higher min Android SDK, the 22 (Android Lollipop 5.1). What do you think @matey97? Are we ready to ditch Android 4?

---

I've noticed something strange. The first time that I run the demo and it asks for the permissions, the callback returns automatically right after asking for them saying that no permission has been granted. This happens in the device that I have here with me and also in the emulator. Digging a bit in the problem, I've found that it is because NativeScript calling the application event when the permissions are requested and now when the permission-asking dialog closes. Could you check please if this happens to you too? Thanks

[matey97]

Hi @agonper,

The API remains the same. But it requires a higher min Android SDK, the 22 (Android Lollipop 5.1). What do you think @matey97? Are we ready to ditch Android 4?

Time to get rid of those ancient devices ☠️.

I've noticed something strange. The first time that I run the demo and it asks for the permissions, the callback returns automatically right after asking for them saying that no permission has been granted. This happens in the device that I have here with me and also in the emulator. Digging a bit in the problem, I've found that it is because NativeScript calling the application event when the permissions are requested and now when the permission-asking dialog closes. Could you check please if this happens to you too? Thanks

I've tested the demo with an Android 9 and an Android 11. The Android 11 seems to behave as you described and some logs with permission errors are printed. The Android 9 works as expected (no error logs), but the application events are being called in the same way as in Android 11 (resume/suspend on dialogs, if I understood well). The only difference between both versions is the activity recognition permission, not required in Android 9. My hypothesis is that requesting both permissions at the same time is causing troubles 🫣.

Anyway, I don't think it's an issue with the plugin itself.

[agonper]

Hi @matey97!

Time to get rid of those ancient devices ☠️.

Hahahaha (agree 😈 )

I've tested the demo with an Android 9 and an Android 11. The Android 11 seems to behave as you described and some logs with permission errors are printed. The Android 9 works as expected (no error logs), but the application events are being called in the same way as in Android 11 (resume/suspend on dialogs, if I understood well). The only difference between both versions is the activity recognition permission, not required in Android 9. My hypothesis is that requesting both permissions at the same time is causing troubles 🫣.

You completely hit the nail! I was working on the NS8 version of the plugin and this was giving me lots of problems, so I decided to do the different actions in a sequence, and... 🎉 it was that hehe. In the NTD we prepare the tasks sequentially, that's why we weren't facing this issue until now...

Thanks for the feedback!