I am trying ionic push notification, i got device token in browser, but i idid not get device token in my phone.
I got this error
please help.
Based from this forum, there might be something wrong with your Google account. Try these:
Go to Settings -> Applications -> Manage applications -> All
Select "Clear data" for "Google Play services" and "Google services framework"
Temporarily unlink your Google account from the phone
Reboot the phone
Re-associate your Google account
Also take note that GCM only works on devices that run android 2.2 or newer. Also GCM only works if a google account is installed for the device. This is the reason Google recommended using <uses-permission android:name="android.permission.GET_ACCOUNTS" /> in the manifest so you are sure the device has a google account.
Check this link.
Related
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.
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.
currently I'm facing a problem about firebase phone authentication.
Whenever I searched the problem in SO, everybody said that "Android Device Verification" API shall be enabled, but the API is not searched on GCP.
You can find the Android Device Verification service here.
Ensure you have enabled Android Device Check API and you have added your SHA256 to the Firebase Console.
I'm creating an app with Unity3d 2019.2.9f1, and trying to utilize Google Cloud Storage as a data store of asset bundle.
In some users' environment, there were network errors below:
400 GET https://storage.googleapis.com/storage/v1/b/...
'Unable to complete SSL connection' response: 'Unable to complete SSL connection'
This error occurred in Samsung S7 edge、Redmi Note 7S, but wasn't seen in iPhone or many other android devices.
If anyone knows about this error, please help me...
I asked one user who was facing the error to go directly to the storage.googleapis.com link in his Google Chrome app, and it failed with "net::ERR_CONNECTION_CLOSED".
However, by shutting down and restarting device and uninstall&reinstalling the app from Google Play Store, he said the app started to work fine.... So anyway it seems it was solved🙌
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.