-
Notifications
You must be signed in to change notification settings - Fork 16
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
Error while lauching my app #6
Comments
Thank you for your submission, we will try to reproduce this issue and get back to you with solution. |
Hello. |
Same issue here. Tried it with a physical android device (OS 11) and an android emulator, but the issue persists. Doctor summary (to see all details, run flutter doctor -v): |
I get the same issue with the following message:
I followed these instructions, but this did not change the outcome: I get this in release and debug on a physical device using android 11. Please meet my doctor:
|
This issue does not happen for me on a new blank flutter app. |
Here is the content of my
For the working project:
The
I aligned the
Here is why I had to keep
I still get the same error message while the empty project runs freerasp. Is there another difference I should try to detect? |
Hello.
|
Hi @talsec-app , Thanks for your help! I just tried the following:
I still get the same error message.
I will now try removing the plugins one by one. |
I finally got rid of all the plugins in my project and I still have the same issue. Is there something else I can do? |
I got it to work with a non-functional project. I rolled back to before the null-safety migration and the plugins removal, I added the So, my issue was the missing |
Hello. Thank you for your work. We can confirm that issue is caused by this problem. Our plugin was written when null-safety was out for quite a long time. Our constructor uses expectedSigningHash, expectedPackageName (in AndroidConfig) and appBundleId, appTeamId (for IOSConfig) are mandatory. This issue will be fixed in next release. We would like to ask @Pacane and @urbanjagodic if this solved their issue or the issue persists. Thank you for your cooperation. |
Hi @urbanjagodic, does this resolution solve your issue? |
Hello. |
@talsec-app When I start the application, I get an error like this and the application crashes:
|
@talsec-app My code, executed in initState, looks like this: `Future initSecurityState() async {
}` |
Hello @Developer1414 , the app is crashing because there is a missing x86 native module. Flutter officially supports only some ABIs in the release mode, and platform x86 is not included (more information here - https://docs.flutter.dev/deployment/android#what-are-the-supported-target-architectures). Because of that, we decided to distribute our library also without the x86 support. This issue should only affect the development process (as the release mode does not support the x86 platform anyway). If you are running the application on Emulator, we recommend downloading an Android image with supported ABI. If you have any questions, please let us know. Best regards, |
I've trying to run my app using freerasp and when it's launched I get this error at runtime:
When I remove this line
TalsecApp(callback: callback, config: talsecConfig).start();
It's not throwing it anymore.
I have a dependency on freerasp: ^1.1.0
Have you experienced something alike in the past?
The text was updated successfully, but these errors were encountered: