Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

notification not working on android #402

Closed
J0K3RAS opened this issue May 23, 2018 · 3 comments
Closed

notification not working on android #402

J0K3RAS opened this issue May 23, 2018 · 3 comments

Comments

@J0K3RAS
Copy link

J0K3RAS commented May 23, 2018

Lately I've been using the notification.notify(message='test message') on linux with great success
The probem comes when I try it on andoid (using pydroid3 or compiling an apk with kivy), where it gives error: NotImplementedError.

Please note that vibrator.vibrate(10) works fine, and the piece of code tested is the same as the one working on linux.

I can provide you the adb logs from my .apk or the output log from pydroid3 console, in case you cannot reproduce the problem.

The plyer version used on android, is the one that is available on pypi

@akshayaurora
Copy link
Member

python-for-android version?
which toolchain ? sdl2? old_toolchain? py3 crystax?

@J0K3RAS
Copy link
Author

J0K3RAS commented Jul 15, 2018

I don't use python3 crystax

I use the kivy vm with buildozer

Toolchain, sdl2, old_toolchain, are the default versions that come with kivy vm

@morgansong
Copy link

I had same issue. Don't know the reason why main.py works fine with correct notification in win10 laptop but don't work on my android phone after I packed to APK successfully throught the buildozer VM with default setting.

@KeyWeeUsr
Copy link
Contributor

KeyWeeUsr commented Dec 30, 2018

Notifications work properly. Make sure you have android in your requirements. In case it still does not work, make sure you have the latest release and if it still does not, switch to the master branch. It worked for me even with the stable version though on non-Oreo device.

For Oreo+ you'll need to wait for the next release (1.3.3).

@KeyWeeUsr KeyWeeUsr added this to the 1.3.3 milestone Dec 30, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants