-
Based on your question, you are trying to understand why an exception was thrown when attempting to access a function in GA4 admin in your staging testing environment, even though it worked perfectly fine in your development environment. It’s clear that the issues arose primarily during the transition from your development to the staging testing environment.
There could be several reasons for this. One possible reason could be differences between the configurations in the two environments. For example, there might be certain permissions or settings enabled in your development environment that are not enabled in your staging environment.
In terms of the “WEIRD_PROJECT_ID” you asked about in the exception, this sounds like it might be referring to the project ID of your Google Cloud project. If the project ID in the console doesn’t match the one specified in your code or configuration files, this could certainly cause issues. It’s hard to say without more context, but it’s definitely something worth checking out.
Finally, you were asking about the timeline for the beta release and final code of your API. It’s hard to give a definitive answer since this can depend on numerous factors, including the scope of the project, resources available, any issues that might arise during testing, and so on. It would be best to thoroughly test the alpha version of the API and iron out any issues before moving ahead with a beta release.
Without a look at the specifics of your project and its configuration in both environments, these are just general areas to check and think about. Hope this helps in some way!
