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

Accessing hidden method Landroid/os/WorkSource #4

Open
shokarta opened this issue Aug 13, 2024 · 4 comments
Open

Accessing hidden method Landroid/os/WorkSource #4

shokarta opened this issue Aug 13, 2024 · 4 comments

Comments

@shokarta
Copy link

Hello @dantti,
after weeks of figuring this out, I was able to run it via QMake, android SDK used 34, minSDK 28, firebase c++ sdk is current 12.2.0
So I was able to run it and receive the device token :).
but when I send the push notification from firebase console, either directly to one device or to all, I receive the following "warnings"

W mtoro.appMobile: Accessing hidden method Landroid/os/WorkSource;->add(I)Z (unsupported,test-api, reflection, allowed)
W mtoro.appMobile: Accessing hidden method Landroid/os/WorkSource;->add(ILjava/lang/String;)Z (unsupported,test-api, reflection, allowed)
W mtoro.appMobile: Accessing hidden method Landroid/os/WorkSource;->get(I)I (unsupported, reflection, allowed)
W mtoro.appMobile: Accessing hidden method Landroid/os/WorkSource;->getName(I)Ljava/lang/String; (unsupported, reflection, allowed)

and then nothing else happens... no error, no notification, no console debug:
image

  • not sure if function "messageReceived" is even triggered by firebase anymore

when we got this far, would be sad to give up...
by your experience, or at least hunch, dont you have any idea where could be the problem or what to look up as a next step?

@dantti
Copy link
Member

dantti commented Aug 13, 2024

do you get the notification when the app is closed? If not then your server has issues, else when running the messageReceived should be triggered

@shokarta
Copy link
Author

No I dont even when app is closed, but I dont see how this could be server issue. I send notifications directly from firebise console (so not via api myself). and once its sent, the app on device recognize incomping message, and prints the error from issue i reported above. So the apps know notification was received, it just does not know ow to process it (i think)

@shokarta
Copy link
Author

sorry, my mistake... when app is closed, then i receive the notification just fine :)

@dantti
Copy link
Member

dantti commented Aug 13, 2024

right, well then it's an issue on the app side, could be even with the FB C++ sdk, but don't know what it is

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants