Adrien Poupa

> The solution is to also run the composer image as user 1000 Yeah this is precisely what I said here: https://github.com/aschmelyun/docker-compose-laravel/issues/49#issuecomment-651131620 For your existing files, you just need to...

@paranoiasystem this is a different issue, unrelated to permission. It simply means that you need to remove any closure route before caching routes. The error message is self explanatory. https://stackoverflow.com/a/45266424/11989865

You should have one project per docker-compose

Hi, I created a repo just for this purpose :) https://github.com/kabouzeid/Phonograph/commit/beb52bec8c31ff4b78d63366d6f734c18326ad2d

I would be glad to see such as PR :) Let me know if I can help!

@Octoton would your PR fix this?

I guess I need to update my jAudioTagger fork to fix this.

I agree it's not the best way to approach this... but with 75 issues open I just need to declutter things a bit :)

Yes, I think it would be the easiest way to deal with this, however Google's support is a mess as well :p

I was able to create 3.3.0 without submitting a form. A warning was added [here](https://support.google.com/googleplay/android-developer/answer/10467955), stating that this will only affect apps targeting API 30 while we are still targeting...