plyer.uniqueid.id causes crash on Android with sdl2

[WillDHB]

I've found that attempting to access plyer.uniqueid.id causes the app to crash immediately (without any normal exception propagation) on Android. This only happened after switching the backend to sdl2, however; prior to that, everything seemed to work fine (I have been unable to revert back to the old backend to verify this). I have tested this out on two different Android devices with the same result.

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/39672571-plyer-uniqueid-id-causes-crash-on-android-with-sdl2?utm_campaign=plugin&utm_content=tracker%2F77151&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F77151&utm_medium=issues&utm_source=github).

[trivedigaurav]

Could you include the error log please?

[WillDHB]

Probably.

deviceid_log.txt

[WillDHB]

After messing with this some more, it looks like just about anything from plyer causes the issue. After messing around with it, it looks like the problem happens in android/init.py, on the line:
activity = PythonActivity.mActivity

[WillDHB]

It looks like the problem is that org.renpy.android.PythonActivity only works with the old toolchain; org.kivy.android.PythonActivity should be used with the new toolchain.

[KeyWeeUsr]

It looks like the problem is that org.renpy.android.PythonActivity only works with the old toolchain; org.kivy.android.PythonActivity should be used with the new toolchain.

Not necessarily. The problem will happen if you don't include android in your requirements since that actually resolves what JAVA_NAMESPACE is used or better said, that thing chooses between renpy or kivy, otherwise it just fallbacks to the old namespace org.renpy.android.