Bug: Incompatible with latest Capacitor V5 Android Platform
tobiasmuecksch opened this issue · 12 comments
Description
Since I cannot reopen #185, I'm creating this new issue.
After running npx @trapezedev/configure run platform-config.yml (Version 7.0.9, I double checked that) Android Studio isn't able to start the app anymore and shows the following error:
I assume this bug was introduced while fixing #185.
Reproduction
- Clone Repo: https://github.com/tobiasmuecksch/cap5-trapeze-bug
- Install dependencies
npm i - run
ionic cap sync - run
npx @trapezedev/configure run platform-config.yml - run
ionic cap open android - Start the app in an emulator
- See the aforementioned error
I suspect that this particular spot is where things are going wrong:
But I don't know where this is coming from. I've search-and-replaced all occurrences of "io.ionic.starter" but this issue still persists.
I wonder if this is because it's setting some additional manifest fields that aren't expected. I'll double check and improve my tests
Can you try @trapezedev/configure@next? It won't add any more package info to the manifest if there wasn't any there before and will only change the gradle applicationId and namespace
@mlynch I just tested it using npx @trapezedev/configure@next run platform-config.yml, but the error is still there
Did you make sure the changes from the last run were undone first? I will be able to test it again later once i'm back on better internet
I'm 100% sure. I've rolled back all changes and double checked that by starting the app in the emulator (which is working in the original state). Afterwards I re-ran trapeze using npx @trapezedev/configure@next run platform-config.yml and restarted the emulator - the error was back.
I even checked which version of trapeze I'm using npx @trapezedev/configure@next --version (it shows 7.0.10-next.0)
I just tested it, ran into the same issue, and fixed it by invalidating caches and restarting android studio. This appears to just be a bug with android studio caching and not an issue with the tool
@mlynch I'm sorry, I had no idea. I will test it on my machine also and close this issue, if that fixes the problem for me too. Will do it tomorrow.
For anyone running into these issues with the @trapezedev/project package, installing 7.0.10-next.0 resolved the issue for me as Max suggested above 😄.
This issue just saved me an hour or two debugging. Thanks guys!
Sounds like this is working fine then so I'll ship a new latest
@mlynch Yes, I can also confirm it does. Thank you very much! 😃
7.0.10 is live with this fixed