WARNING: API 'variant.getMappingFile()' is obsolete and has been replaced with 'variant.getMappingFileProvider()'.

[samsonpaul87]

I just added the scripts to my build.gradle script. Syncing it up gives me this warning:

WARNING: API 'variant.getMappingFile()' is obsolete and has been replaced with 'variant.getMappingFileProvider()'. It will be removed in version 5.0 of the Android Gradle plugin. For more information, see https://d"}]}

Kindly fix the issue. I am unable to deploy my application to the Play Store, due to this issue.

[suriyasundar92]

Hi @samsonpaul87, We are working on fixing this warning. Will update you as soon as we publish the fix for it.

[suriyasundar92]

Hi @samsonpaul87 We have published a newer version of the plugin(3.0.0).
Please try to use it. Please let us know if you face any issue.
https://plugins.gradle.org/plugin/com.flurry.android.symbols

[samsonpaul87]

@suriyasundar92 Thanks for the fix. I am able to build my application without warnig now 👍 .

Is there any way to check and see the symbols uploaded in Flurry? I am curious to know the output. If there is no any way to check the same in Flurry, then is there any option to see the symbol upload in the build logs, so that we can make sure that the upload-client executed succesfully?

[suriyasundar92]

Hi @samsonpaul87 Could you please give me your company name and application name in flurry so that I can confirm the upload of the symbols from my end ??

[suriyasundar92]

Hi @samsonpaul87, On a second thought I think it would be better if you could send the details, explaining your request for verification of the upload, to support@flurry.com.

[suriyasundar92]

@samsonpaul87
We found a bug in the version that was released yesterday(3.0.0). Please try to use the latest version (3.1.0) that was released today.
You can verify the upload of the mapping files by enabling info level for logging in gradle, by adding the flag --info to the build command. You will find the following log statements.

https://github.com/flurry/upload-clients/blob/master/proguard/src/main/java/com/flurry/proguard/UploadMapping.java#L164
https://github.com/flurry/upload-clients/blob/master/proguard/src/main/java/com/flurry/proguard/UploadMapping.java#L161
https://github.com/flurry/upload-clients/blob/master/proguard/src/main/java/com/flurry/proguard/UploadMapping.java#L158
https://github.com/flurry/upload-clients/blob/master/proguard/src/main/java/com/flurry/proguard/UploadMapping.java#L154

Please reach out to us at support@flurry.com if you face any further issues.

[samsonpaul87]

Thank you @suriyasundar92 . I will try the updated version and monitor the logs for successfull upload.

[samsonpaul87]

@suriyasundar92 I have enabled logging in my gradle file and I can see the following logs in my build. So, I think it's working as expected now. Thank you again for the quick fix you did.

[14:39:04]: ▸ Found project XXXXXXX for api key MRWXXXXXXXXXXXXXG6HV
[14:39:04]: ▸ Created upload with ID: 4XXXX2
[14:39:04]: ▸ ProGuard mapping uploaded to Flurry
[14:39:04]: ▸ Upload completed successfully!

[samsonpaul87]

@suriyasundar92 I have noticed that the above logs are showing only when we generate an APK. But, when we generate an AAB, the logs are not showing up. So, I think it is working only with APK and not AAB.

As AAB is the android's preferred format to deploy new applications, it is not possible for us to deploy an APK to Play Store now. Could you please help me fix the issue.

@suriyasundar92 Is there any other logs that I can check to investigate this scenario further?

[suriyasundar92]

@samsonpaul87 We are looking into the issue. Ill keep you updated on this.

[suriyasundar92]

@samsonpaul87 We have fixed the issue with the plugin so that the mapping files will be uploaded for the task bundleRelease. Please use the latest version of the plugin (3.1.1). Please let us know if you face any issue.

[samsonpaul87]

@suriyasundar92 Thank you for the update. I will try the new version and will let you know how it goes.

[samsonpaul87]

@suriyasundar92 It seems working with AAB now. See the plugin log in the below screenshot. Thank you for fixing this.