Reputation: 33
I have used the pattern 'com.mycompanyname.native.appname' to name the bundle Ids for my apps since years and have created many apps using the keyword "native" in the package name. I didn't get this error when using classic expo builds until I switched to EAS builds. Now, I have to upgrade a few of the live apps, can there be a workaround to overcome this error?
Upvotes: 0
Views: 663
Reputation: 51
Yes, there is a workaround, which is a two step progress:
That way, your applicationId for Play Console stays the same, and the package name used in Java is valid for building.
Here is a gist with an example config plugin, and how to add it to your app.json:
https://gist.github.com/kbrandwijk/cef9e3b01cff91f8dfad8f47f02cb880
Upvotes: 1