codeanticode

No longer relevant as we do package signing through gradle

@rupeshkumar22 thanks for confirming that the export functionality is working! Actually, the project export for AR sketches was broken, but this commit fixed it https://github.com/processing/processing-android/commit/bdde55ade6549fa7f28abf73169e37b61860cc5c :-)

@r1shhh1 thanks for offering to help! According to what @ranaaditya mentioned a while back, a self-hosted maven repo seems like the best option, is that still your view on this...

Looking at #635 sounds like maven publishing is already implemented? haven't tested it, although merged already into main :-)

Learned how to create a maven repo and host it on GitHub (different from [GitHub packages](https://docs.github.com/en/packages/learn-github-packages/introduction-to-github-packages), which requires authentication even for importing the dependencies. 4.5.0b5 artifacts are currently available in...

@victordiaz let me know if you can use the new self-hosted repo: https://github.com/processing/processing-android/tree/repository I have tested with a library project and looks good.

done :-)

Solved by including the processing-android dep from the self-hosted repo: https://github.com/processing/processing-android/issues/623

No longer needed as the mode uses gradle to create the packages and bundles.

Using the ```--skin``` argument (https://github.com/processing/processing-android/commit/806def28a1dfe4bdba9d1714f4bab04dc493450b) and with recent device art pulled from Android Studio (https://github.com/processing/processing-android/commit/e254f20063265ca6646692a887bb1d2b8e51cbcd, https://github.com/processing/processing-android/commit/2ad6507e2e81179fb4c7ddf23f2caae2e5d30bce) seems to solve most of the issues with the emulator