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

Problems with EasyAR (invalid key on Release/Production Mode) #483

Open
von-maurus opened this issue Oct 19, 2021 · 3 comments
Open

Problems with EasyAR (invalid key on Release/Production Mode) #483

von-maurus opened this issue Oct 19, 2021 · 3 comments
Labels
android This issue is specific to the Android Platform. External libs This issue is related to including and stripping of external libraries

Comments

@von-maurus
Copy link

von-maurus commented Oct 19, 2021

Hello!, I have a flutter app with a Unity Easy AR application which requires a Key in order to work. When I build in Debug Mode it works fine, no errors, but the problem is that when I make a build or immediately launch a project on the device in Release-mode , I get an error: Invalid Key. But at the same time, the application package ID and the key itself are 100% correct. This was tested on Android Device.

Steps to reproduce the behavior:

  1. Integrate Easy AR in your Unity Project (works fine)
  2. Export to Flutter following the steps on this Plugin
  3. Test it on debug mode (works fine)
  4. Generate a Release APK (fat).
  5. Get a an error like: "Invalid Key Get from EasyAR Develop Center (www.easyar.com) -> SD Authorization"

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
This is the error shown
image

Unity (please complete the following information):

  • OS: Android
  • Version: 2019.4.28.f1

Device version

  • Device: All Android devices
  • OS: Android
  • Version: SDK 24 or later

Additional context
The assumptions are the following:

  • Is not a Key version problem because I have a Pro Key generated with enhanced features.
  • The error prompt by EasyAR is very poor (invalid key message shown in image).
  • I'm assuming that an EasyAR library maybe gets eliminated or erased when a Release version is build.
  • Maybe the package name changes when a release apk is generated.
  • I checked 100% the package names and

If someone has a better way on doing AR apps using Vuforia or EasyAR please share some knowledge because the issues found didn't work for me. Here are some issues related to this bug:

@MTM-A
Copy link

MTM-A commented Nov 2, 2021

I have the same problem, in debug it works fine while in release it says invalid key.
I verified that the application id is the same as the one I entered in the license on the easyar website.
I also tried to modify the bundle id in unity but the situation doesn't change.

Anyone know what it could be due to and how to fix it ??

@von-maurus von-maurus changed the title Problems with EasyAR (invalid key) Problems with EasyAR (invalid key on Release/Production Mode) Nov 2, 2021
@MTM-A
Copy link

MTM-A commented Nov 29, 2021

@von-maurus, were you able to solve this problem?
Or, does anyone else know how to fix it?

@iletai
Copy link

iletai commented Apr 17, 2022

I facing the same issues with AR Core and Unity Camera freeze in the release build.

@timbotimbo timbotimbo added android This issue is specific to the Android Platform. External libs This issue is related to including and stripping of external libraries labels Jan 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
android This issue is specific to the Android Platform. External libs This issue is related to including and stripping of external libraries
Projects
None yet
Development

No branches or pull requests

4 participants