Any Update of firebase-dispatcher library for targ

问题:

I recently get the warning to update the Android Target Version to 26 or more from the Google Play Console. However, I have already set the target SDK to 26.

I check the AndroidManifest file and the merged manifest for all the libraries I have included in the project.

There are few libraries which are under Manifest Sources and few are under the Other manifest files(Included in merge, but did not contribute any elements) - what does this mean?

Can i update the manifest to target API 26 for this project only and upload the to see if it gets accepted or not.

Google needs to verify the App for SMS and Call Log permission but when i upload the app to the play store i get the warning - •

Your app needs to be using runtime permissions for us to complete the review. Please update your app to target API level 26 or above and resubmit the declaration form.

回答1:

There are few libraries which are under Manifest Sources and few are under the Other manifest files(Included in merge, but did not contribute any elements) - what does this mean?

When you use other libraries their manifest files will merge with yours to form one Manifest that will ultimately be used.

Can i update the manifest to target API 26 for this project only and upload the to see if it gets accepted or not.

It's better to set the minSdkVersion and targetSdkVersion in your build.gradle file not in the manifest because Gradle overrides the manifest values reference can be found here

Google needs to verify the App for SMS and Call Log permission but when i upload the app to the play store i get the warning

When you target API 23 or above you need to write Runtime permissions or you will get a crash when you try to access them.

回答2:

it's called WorkManager now; the Firebase Job-Dispatcher might not receive updates anymore.

implementation "android.arch.work:work-firebase:1.0.0-alpha11"
androidTestImplementation ("android.arch.work:work-testing:1.0.0-beta01") {
    exclude group: "android.arch.work"
}

only the API level of the application package matters - and the run-time permissions need to function - except these critical permissions for SMS and Call Log, which are subject to review. recently had one install from US territory, which might have been such review, even if I only use SIP telephony. there might have been people sending premium SMS from apps, which quickly deduct prepaid credits - or providing robocall services with phone numbers to bother. also smartTAN depends on SMS. the attack vector is realistic, therefore these checks are in place for a reason.