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

Crash on API34 #38

Open
harrypotter06 opened this issue Sep 28, 2024 · 9 comments
Open

Crash on API34 #38

harrypotter06 opened this issue Sep 28, 2024 · 9 comments

Comments

@harrypotter06
Copy link

Hello,

With API 34, I keep having Flic2 crash after about 24 hours.

I use Visual Studio. I created an aar with Android Studio and then integrated it into the Android project as a DLL using Visual Studio.

As the error does not appear under API 33 and lower, it must be a special feature for API34 that was obviously not taken into account.

The Android permissions are all set correctly and are also present.

@Emill
Copy link
Contributor

Emill commented Sep 28, 2024

Can you show me the stack trace or other useful information about the crash?

@harrypotter06
Copy link
Author

Yes. Thats all what we got:

Time: {0}
Error: Unhandled Exception
{1}

@Emill
Copy link
Contributor

Emill commented Sep 28, 2024

Without further info, how do you know the exception originates from this library and not something else in your app? I can't think of anything in our code that would automatically throw an exception after 24 hours.

@harrypotter06
Copy link
Author

Its verry simple:

Android Devices lower API34 - Same App didn't have any crashes (with connected Flic-Button)
Android Devices with API34 and w/o FlicButton, didn't crash

@Emill
Copy link
Contributor

Emill commented Sep 28, 2024

Maybe you can upload a "minimum reproducible sample app" (with source code) that I can run that demonstrates the issue?

@harrypotter06
Copy link
Author

Sorry, i have no sample-app.
The question is verry simple. What are different about API33 and API34 and what modifications for API34 are required.

@Emill
Copy link
Contributor

Emill commented Sep 28, 2024

Here are the new requirements: https://developer.android.com/about/versions/14/behavior-changes-14.

I can't see anything there that would directly affect the code in this library, but maybe you have something else in your app that is affected?

@harrypotter06
Copy link
Author

Hi,

thanks for the lin. Now i have checked this. This error ar not from my code, because for all ERROR in my code, i have a subroutin that generate LOG if the error from my code.

As external code, i only use Flic2Lib. So only the Flic2lib can generate a error that i posted.
So now, i add a permission to the Flic2lib and next day i will see, if i get the error again.

Update i send next days

@harrypotter06
Copy link
Author

But what i saw: If the crash get, after that Flic2lib will rescan Flic-buttons.

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