Currently, my Unity Android app that I uploaded as a production on Google Play has a big problem.
We started Google As advertisement and checked the inflow of users (installation of 1,597),
However, there are only 67 users who have actually accessed it...
I downloaded my app that I uploaded to Google Play directly and logged in with my Google account, so there was no problem, and I asked my friend to download and run the app, so there was no problem logging in.
The predictable problem is that due to the number of concurrent users, many users are unable to access when starting the advertisement, or something seems to be wrong with my GPGS setting.
Please check the possible problems and the image of my GPGS setup.
**Setting **
Unity Ver : 2021.3.8f1
GPGS Plugin : 0.10.14
State
Upload Google Console Production
Google Console -> Play Games Services -> Setup And Management -> Configuration -> Publish Complete
Create 3 Google Cloud Platform OAuth Clients
-> Upload key, app signature key, server
1. Suspected Problem 1
If the AndroidManifest.xml Package Name is different from the package name of the Google Console, can the Production user not access it?
Unity -> PlaySetting -> Identification -> Package Name is entered as the package name of the Google Console, but AndroidManifest.xml Package Name is marked as package="com.google.example.games.mainlibproj" and modified it directly to the package name of the Google Console, but it was restored again.
enter image description here
enter image description here
(If it is a problem and you need to check the Unity error list, you can attach it later)
2. Suspected Problem 2
Can't the user access because Unity's keystore certificate is set to upload authentication signature, not app authentication signature?
enter image description here
3. If you have any other problems, please give us your opinion.
Related
I implemented google login in flutter without using firebase in flutter (google cloud console). It was working in apk then later I needed push notification service for which I used firebase (fcm token and all) then I released the app to playstore but google login does not work. I keep getting apiexception error. Has anybody faced this issue? if yes any help would be highly appreciated.
I do not have a specific answer to your problem but I have also faced this problem once, I accidentally resolved it though.
But Error 12500 is a general error code that may occur when attempting to use the Google Sign-In feature and is caused by a few potensial issues:
An issue with the SHA-1 fingerprint of your app's signing
certificate: To use Google Sign-In, you need to configure your app's
SHA-1 fingerprint and package name in the Firebase console. Make
sure that the fingerprint and package name you have configured in
the Firebase console match the ones you are using to sign your app.
An issue with the Google Services configuration file: Make sure you
have properly added the Google Services configuration file to your
app.
An issue with the Google Play Services library: Make sure you have
the latest version of the Google Play Services library installed in
your app.
An issue with the device or emulator you are using: Make sure you
are testing on a device or emulator that has Google Play Services
installed and is up to date.
Possible fixes to try/check:
Double-check the SHA-1 fingerprint and package name: Make sure that
the SHA-1 fingerprint and package name you have configured in the
Firebase console match the ones you are using to sign your app.
Make sure you have added the Google Services configuration file: The
Google Services configuration file is required for your app to
communicate with Google services, including Google Sign-In. Make
sure you have properly added this file to your app.
Update the Google Play Services library: Make sure you have the
latest version of the Google Play Services library installed in your
app. You can check for updates by going to the "SDK Manager" in
Android Studio.
Test on a device or emulator with Google Play Services installed:
Make sure you are testing on a device or emulator that has Google
Play Services installed and is up to date.
I hope this helps! I will quickly search if I can find any other solution.
Hi I am setting up the MoPub GDPR Android SDK, am getting a call to the consent dialog page on the web but get this response :
05-16 11:10:46.469 13030-13152/ E/Volley: [18308] BasicNetwork.performRequest: Unexpected response code 400 for https://ads.mopub.com/m/gdpr_consent_dialog
This means "Bad Request" and that the call is corrupt I think. Has anyone got this call to work ?
This isn't an ideal solution, but it works.
On your test device install a VPN service app, there are lots of free ones available out there. If you're running in an emulator (or a device without Google Play) you can goto one of the many APK mirror sites to download and sideload the APK directly.
I won't get into the obvious risks of using VPNs, or sideloading apks outside of google play, but if you're paranoid just spin up an emulator to test this.
It's important the service offers VPN servers located in countries affected by GDPR.
Enable the VPN service on your device/emulator and make sure you're using a server located in a GDPR country (Germany, for example). Load up the app your testing, and it should now appear that you are accessing
Not sure why Pete is suggesting a VPN here. But it appears I was getting this error because I forgot to replace the AD_UNIT_ID in the SdkConfiguration.Builder with my Ad Unit ID.
when I run the Google smart home demo, I have a problem at 25.Find your app in the list of providers. The result is that I can’t find my APP in Home control use the Google Pixel device.
I am sure that:
1、I use the same google account to create the project in web and login in google home App on Google Pixel, and I launch the test in 30 mins which mean that the test shouldn’t be expired.
2、I have done the command "gactions test --action_package PACKAGE_NAME --project PROJECT_ID"
Could you any body gave me some suggestions? I have sticked it for more than two weeks.
The Google smart home demo you mentioned is to help you build web service to process Google smart home requests. After building web service and host it on some public URL, you have to specify this URL in your action.json.
Also you need to build your OAuth 2.0 server and specify it in project setting in AoG console.
Then after executing"gactions test --action_package PACKAGE_NAME --project PROJECT_ID", you shold see your app [test]YOUR_APP_NAME in the add devices section.
Please check if you miss any part above and your gactions command runs without error messages.
Good luck~
I try to upload sample app to Google App Engine with existing progect ID.
Here is GAE screenshot
gae screenshot
I'm using the same ID in the progect.
But when I try to upload it with plugin from Eclipse then I recive an error:
eclipse error
The whole error from a console:
------------ Deploying frontend ------------
Preparing to deploy:
Created staging directory at: 'C:\Users\User\AppData\Local\Temp\appcfg2693799039714166602.tmp'
Scanning for jsp files.
Scanning files on local disk.
Initiating update.
com.google.appengine.tools.admin.HttpIoException: Error posting to URL: https://appengine.google.com/api/appversion/create?app_id=app1-152711&version=1&
404 Not Found
This application does not exist (project_id=u'app1-152711'). To create an App Engine application in this project, run "gcloud beta app create" in your console.
Debugging information may be found in C:\Users\User\AppData\Local\Temp\appengine-deploy7186088524405894873.log
Why I can not upload it?
This is actually the new intended behavior. App Engine will not be enabled for new projects until you go through the app creation flow in the Cloud Console under 'App Engine' to enable the App Engine service, or alternatively run gcloud beta app create from the console.
I just encountered this myself. The project has to be created in the Cloud Console AND you need to go through the project setup in AppEngine. Something must be broken in the API that creates the AppEngine part of the process while uploading. So doing it through the web interface creates the project for you... and then uploading will essentially fill it in.
It never used to be this way, so maybe something changed.
I have the same problem. This is what I did to solve it.
Log in to your google cloud account.
Select your project from the blue header bar.
Click the menu button(the 3 bars) on the top left of blue header bar.
Select IAM - you should permission for App Engine Service account. If not, you have to set it up.
To do that:
Click the menu button (the 3 bars) again
Click the App Engine
If you have not set it up, you will be prompt to do a tutorial.
Cancel the tutorial.
Go back to IAM.
Now you should see that the App Engine Service account added to the permission
Go ahead to upload. Should work now.
Make sure you are logged in with the correct Gmail account. At the bottom right corner of Eclipse you will see which account you have authorized, or you will see "Sign in to Google" - click on it to authorize Eclipse.
We've been getting this installation error when our users try to install the apps marketplace app.
How do we resolve this?
Is the error being seen by Google Apps domain administrators or non-admin domain users? If its latter then its likely the domain administrator has not enabled install for non-admin users in the domain.
I've figured out the issue but do not know how to resolve this.
We had tried to update our marketplace app manifest file but due to some issue on Google's end, the updated manifest file was not being uploaded and this error was being thrown
This item is not an app, please remove app section from manifest , google apps marketplace
So we removed the "app" section from the manifest file and uploaded it. This has resulted in our marketplace app becoming a Chrome extension rather than a marketplace app and causing the issue.
Currently if I try to edit and upload a version of manifest file with "app" section, it won't allow me to upload it, showing the same error as before. So there is no way that I know which can solve this issue.
If anyone can help me out with this it will be really helpful. Registering a new MP app, getting approval from google and moving all users and reviews to new app will be really painful.