Hi all,
I am having trouble proving my package name ownership to google console. Some background: I’ve created APK files via gdevelop so I think that is why google says my package name is owned already.
- When I create an app with my package name, I get this message:
“To finish registering this package name, prove that you own it by completing the following tasks.”
- When I try to upload an APK file, I see this instruction:
“To finish proving ownership of com.xxx.yyy, sign an APK with the private key that corresponds to the public key you provided, and upload the APK”
- When I upload my APK file that I created directly from gdevelop, I get this error:
“The uploaded APK does not have the required token file.”
I don’t know if my only solution is to just change my package name and create the app on the google console first before creating anything in gdevelop. Is there any other solution for me that doesn’t require me changing my package name? Is anyone else having a similar issue or had a similar issue in the past?
Thanks in advance for any advice or suggestions!
1 Like
Hi there,
I am encountering the exact same issue with my latest project. No matter how I try to bundle the app, I keep getting the error: “The uploaded APK does not have the required token file.”
The root of the problem is that Google’s new verification policy requires the adi-registration.properties file to be placed specifically in the native root assets/ directory of the signed APK. Currently, the GDevelop cloud build system “wraps” resources in a way that makes this token invisible to Google’s automated verification tool.
I believe it is time for GDevelop to update its build engine to support these new Google Play Console requirements. We need a native way to include these verification tokens or a specific “Ownership Verification Build” mode that allows us to comply with Google’s latest security and ownership policies without having to resort to complex manual build workarounds (like Docker or manual APK signing).
This is becoming a major roadblock for developers trying to launch new apps under their own package names. Hopefully, the GDevelop team can look into this and provide an official update to streamline this process.
Has anyone else found a workaround that doesn’t involve a complete manual Android Studio build?
I have been working on a simple, everything included manual output, to whatever you desire. AAB, APK and APK debug. Take a look. It will change from HTML 5 to Android manual export later but what you think? And the environment stuff i will include some files that help people instant set-up and make their games. So no fiddling with Android studio and so on.
NOTE: It's not finshed and some features are missing
1 Like
