Skip to content

Conversation

@Inakitajes
Copy link
Contributor

A mixed subset of devices is crashing due to an Unsatisfied Link Error.

The try-catch has already been corrected to precisely capture the generated error. A throwable try-catch has been added defensively to prioritize avoiding crashes. Since this is deinitialization code, it is at an unrecoverable point, so it is safe to do so.

We released this patch to production in our application last week, and it finally seems to be resolved. So it should be safe to close #39

The reasons for this error occurring originally have not yet been determined. It could be due to race conditions during the deinitialization of modules and libraries, or due to incompatibility with specific devices. However, the range of devices, brands, operating system versions, and others is quite broad, making it a difficult issue to debug.

@Knightro63 Knightro63 merged commit 042e6ad into Knightro63:main Dec 4, 2025
1 check failed
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

Successfully merging this pull request may close these issues.

UnsatisfiedLinkError when FlutterAnglePlugin deinitializes

2 participants