I want to use the react-native-maps package in my react-native app and this package needs the latest version of google play services to work properly. I want to host an APK of google play services in somewhere and refer the users to download it if the version of their google play services is out of date.I want to know is there any universal version of google play services that is compatible with all android devices?
I think the (030) version of google play services will work on every version.
Well, You are trying to use latest/updated version of google-play-services. In react-native-maps Maybe they are using updated one. Or I'm assuming they are using out of date one.
If you want to use updated one first fix that which one you want to use then do like below: skip react-native-maps google-play-services version and use your own defined.
compile (project(':react-native-maps')) {
// exclude version their version
exclude group: 'com.google.android.gms', module: 'play-services-base'
exclude group: 'com.google.android.gms', module: 'play-services-maps'
}
//user your own
compile 'com.google.android.gms:play-services-base:X.x.x'
compile 'com.google.android.gms:play-services-maps:X.x.x'
Thanks if you have any query you can ask me and for Gradle dependency, you can learn more from here
Related
I recently updated my Flutter app with Appodeal ads, later I got a message.
Google Play Console:
Your app **** version code *** includes SDK com.my.tracker:mytracker-sdk or an SDK that one of your libraries depends on, which collects personal or sensitive data that includes but may not be limited to Advertising ID, Android ID, Device Wifi MAC identifiers. Persistent device identifiers may not be linked to other personal and sensitive user data or resettable device identifiers as described in the User Data policy.
where can I find in my app SDK com.my.tracker:mytracker-sdk
app>build.gradle
dependencies {
implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:$kotlin_version"
testImplementation 'junit:junit:4.12'
androidTestImplementation 'androidx.test:runner:1.1.1'
androidTestImplementation 'androidx.test.espresso:espresso-core:3.1.1'
implementation 'com.google.firebase:firebase-analytics:21.1.1'
implementation ('com.appodeal.ads:sdk:3.0.0.+') {
exclude group: 'com.appodeal.ads.sdk.services', module: 'adjust'
exclude group: 'com.appodeal.ads.sdk.services', module: 'appsflyer'
exclude group: 'com.appodeal.ads.sdk.services', module: 'firebase'
exclude group: 'com.appodeal.ads.sdk.services', module: 'facebook_analytics'
}
implementation 'com.appodeal.ads.sdk.services:firebase:3.0.0.+'
}
How to make persistent device identifiers not be linked to other personal and sensitive user data or resettable device identifiers??
How should I resolve this problem. Do I really need to stop advertising (using appodeal)?
Message i got from Appodeal support. and it seems to work
Currently, MyTracker has released an updated version, 3.0.9, which
includes all necessary fixes and to update the MyTracker library,
please resync your dependencies file with all dependencies, and the
new MyTracker version will be downloaded automatically.
myTracker is included in the myTarget SDK, which is part of the Appodeal SDK.
Try to exclude the myTarget adapter in the build.gradle
exclude group: 'com.appodeal.ads.sdk.networks', module: 'my_target'
I did an update to version 3.0.9 instead an error occurred, then I changed it to 3.0.0.4 with normal success. Will this version 3.0.0.4 also still get SDK violation warnings from Google Play
In my project I'm compiling against sdk-version 23 and using the compat/support libraries version 23.2.0.
Now I'm trying to update the play-services-version from 9.2.1 to 10.2.0
compile 'com.google.android.gms:play-services-base:10.2.0'
But making this change ads the com.android.support:support-v4:24.0.0 library to my project making my project to crash due with strange not found errors in the compat libraries like explained in this question.
How can I avoid that? should I skip the play-services update? can I avoid them to raise the version of the support-v4 lib?
Maybe it could work with something like this:
compile('com.google.android.gms:play-services-base:10.2.0') {
exclude group: 'com.android.support'
}
or if this does not work then maybe:
compile('com.google.android.gms:play-services-base:10.2.0') {
exclude group: 'com.android.support', module: 'support-v4'
}
Or maybe you don't need the whole base play services and only specific packages as defined here
I implemented new module for an application, using a 3rd party library. In this library, they used com.google.android.gms:play-services-base:9.0.2, and in the original application, they used com.google.android.gms:play-services:4.3.23. So there was a conflict and I can't sync gradle at all. Is there anyway to fix this conflict ? update google play service of the original project is out of question, because the amount of work would be tremendous.
please reefer this ref: https://developers.google.com/android/guides/setup
and add google play service in your gradle
From version 6.5, you can instead selectively compile Google Play service APIs into your app.
try to do something like this
compile ('com.android.support:recyclerview-v7:22.2.0') {
exclude module: 'support-v4'
}
I know about this question but I don't think it helps me and the problem looks slightly different.
I'm doing this app where I need to implement AppsFlyer for tracking and I'm required to use only 2 components from Google Play Services:
com.google.android.gms:play-services-ads
com.google.android.gms:play-services-gcm
And I'm using the latest version of the Google Play Services, 9.0.2 that is.
The problem is that on the first app launch after installing the app, the app takes quite a bit of time to start. There's no log output and when the app starts doing something, the first line on the log is:
06-16 16:50:23.782 22368-22368/com.company.app I/FirebaseInitProvider:
FirebaseApp initialization unsuccessful
I'm not using Firebase, how can I get rid of this? It really slows down the application initialization. Not a very good user experience...
EDIT:
I've added both libs, one at a time and I've realized that the GCM is the one causing the issue. When I add:
com.google.android.gms:play-services-gcm
I start getting the "FirebaseApp initialization unsuccessful" log and the app takes a while to start. Perhaps downgrading "fixes" the problem, but that's not a very good solution.
I would suggest you to exclude the firebase group using gradle:
compile('com.google.android.gms:play-services-ads:9.0.2') {
exclude group: 'com.google.firebase', module: 'firebase-common'
}
compile('com.google.android.gms:play-services-gcm:9.0.2') {
exclude group: 'com.google.firebase', module: 'firebase-common'
}
Or, simply apply a global exclude configuration, like this:
configurations {
all*.exclude group: 'com.google.firebase', module: 'firebase-common'
}
Hope it helps :)
I had the same issue and not only I had to downgrade the services but also gradle version.
In my case I had (in app/build.gradle)
compile 'com.google.android.gms:play-services-location:9.0.2'
compile 'com.google.android.gms:play-services-maps:9.0.2'
compile 'com.google.android.gms:play-services-gcm:9.0.2'
and (in build.gradle)
classpath 'com.android.tools.build:gradle:2.1.2'
After changing services back to 8.4.0 and gradle to 1.5.0 (Probably higher version is fine also but it was the one I had before upgrading to 2.1.2) everything is fine and FirebaseApp initialization is gone.
Maybe it's not the best solution but I couldn't find anything else.
This question already has answers here:
Google Play: We found Ad SDKs in your application
(5 answers)
Closed 7 years ago.
I've got an Android application that is being submitted to the Play Store. That application is built using the same Gradle build script but has several different product flavors being built which just set properties for different application ID's and names for each different flavor.
The problem we have is that AdMob is 'not' included in the build script, but some of the build flavors that are being submitted the Play Store is reporting that AdMob was found in the application. But other flavors (built from same build script) are accepted fine without any AdMob notification.
Has anyone seen this issue and possibly know what might be triggering it? Besides our own internal libraries, this is what's being included in the dependencies of the build script:
dependencies {
compile 'com.actionbarsherlock:actionbarsherlock:4.4.0#aar'
compile group: 'com.android.support', name: 'support-v4', version: '21.0.3'
compile 'com.crashlytics.android:crashlytics:1.+'
compile 'com.google.android.gms:play-services:6.5.87'
// ViewPagerIndicator Library
compile 'com.viewpagerindicator:library:2.4.1#aar'
compile fileTree(dir: 'libs', include: '*.jar')
}
I've checked the 'libs' directory but we only have 3 jar files in it that have just some included class files so there isn't any SDK's in that directory.
This is what the Play Store is reporting:
In your gradle build script you have:
compile 'com.google.android.gms:play-services:6.5.87'
This means that all Google play services are included into your project (including AdMob as well).
Instead, you should include only play services that you need. For example:
compile 'com.google.android.gms:play-services-fitness:8.3.0'
compile 'com.google.android.gms:play-services-wearable:8.3.0'
Take a look at this guidelines.
You are using Google Play Services which includes Admob.
You can exclude Admob by only referencing the Google Play Services libraries you actually require instead of the complete set.
More details here on how to do that:
More Permissions in uploaded apk than in manifest file