Raphaelrex_Xin

I had the same issue here recently. The error message also includes audioservice like you do (which I assume could be caused by some conflict between audioservice and awesome notification)....

> There is nothing to do with audio. Its the method to get the main class name. This is the only way to tell to OS who he needs to...

> Can you provide us some log information or anything else that cold help us to figure out whats going on? I only have error messages from Google Crashlytics, and...

> The error is right here: > > https://github.com/rafaelsetragni/awesome_notifications/blob/3f5c77193d2ad47fb8d49e677a1fa9a37b9dd6bb/android/src/main/java/me/carda/awesome_notifications/AwesomeNotificationsPlugin.java#L184 > > mainTargetClassName needs to have the main class name of your application. I dont know why your app does not...

I'm starting to see the issue again after reducing number of activity to 1 in AndroidManifest.xml, so issue is not related to that. Could you give me a hint on...

I used your 0.7.0 beta and it is so far so good. But in the meantime, I also updated the related plugin audio_service to their latest version 0.18.4. Worth mentioning...

The solution seems great! Will this beta version be released any time soon?

Hi, any progress on this? I also encountered this in system_tray 0.0.7.