I am trying to integrate ads in my android app through Heyzap. However, when i open the heyzap mediation suite, some of the third party sdks are marked with "missing permissions". these are AdColony, AppLovin, ChartBoost and Vungle. They all have "Sdk detected", "all activities found" and "credentials found" marked with green. the other sdks have "all permissions found". The thing is that when the app is trying to fetch an add it crashes.
What I would like to know if these crashes have anything to do with the sdks with missing permissions and if yes, how can i solve this problem?
I read "how to"s for each sdk and put all the mentioned permissions in my manifest but still nothing.
Can you, please, help me?
I was getting the same Missing Permissions error for Vungle, Applovin, Chartboost and AdColony.
For me removing android:maxSdkVersion="18" from the WRITE_EXTERNAL_STORAGE permission in the Vungle manifest made the issue disappear for all four networks. By Vungle manifest I mean the AndroidManifest file in Plugins/Android/Vungle_lib
As per Google specification the permission is not needed any more for API level 19 and above so I guess that's why Vungle adds the parameter. But somehow the Heyzap Mediation Suite keeps telling us that we are missing permissions. My guess is that there's something wrong with the Heyzap Mediation Suite since ad serving works even with the Missing Permissions warning.
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.
I am using the flutter health package. It is working fine on iOS but on Android, it kept saying "Authorization is not granted".
I followed the example to get the fitness API on the google developer console and OAuth Client ID. But I don't know how to set it in my flutter app if it is needed. Thank you.
I've got it working by following this advice on the package Github repo. But I am open to more answers. Thanks
[Updated]
This solution can cause conflict and raise the "version solving failed" exception when using it together with the location package.
The best way, for now, is to use health: 3.0.4 as a workaround.
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.
I am trying to setup Firebase in my Nativescript app(Angular 2- TypeScript). However, It prompts me the error as below.
A valid Facebook app id must be set in the AndroidManifest.xml or set by calling Facebook.setApplicationId before Initializing the sdk.
Why should I provide the Facebook app ID for the start-up?
Any idea?
Much appreciate.
I have resolved by reinstalling the native-script-firebase-plugin without initialized the Facebook's Authentication for this error message "A valid Facebook app id must be set in the AndroidManifest.xml or set by calling Facebook.setApplicationId before Initializing the SDK"
As for the second error message "Google Play Service is required on this device", I just installed and upgraded the Google Play Service on the particular Android Emulator, and it works fine now.
In conclusion, is worth to check the Google Play Service it has been installed and upgraded to the appropriate version or not.
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.