Proguard mapping file not included inside debug_meta on flutter application

[lberaldodev]

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

1. Flutter application (3.19.6)

2. Sentry 4.2.0

3. Build.gradle settings includeProguardMapping = true autoUploadProguardMapping = true dexguardEnabled = true uploadNativeSymbols = true autoUploadNativeSymbols = true includeNativeSources = true includeSourceContext = true

4. Check if proguard file was uploaded

5. Check if debug files includes proguard file

6. Check the json issue

Expected Result

When we upload the proguard mapping file, we expect to see the full stack trace

Actual Result

No stacktrace included and no proguard type included on debug_meta

Product Area

Issues - Source Maps

Link

No response

DSN

No response

Version

No response

[getsantry[bot]]

Auto-routing to @getsentry/product-owners-issues for triage ⏲️

[scttcper]

Does the issue have the release set?

[lberaldodev]

Does the issue have the release set?

Yes, the release is set to each proguard correctly. We can inspect the release oppening the link from the image below

[scttcper]

I mean does the issue have a release tag

[lberaldodev]

I mean does the issue have a release tag

My bad :) I don't think so...

It's a very old problem here at my project, he already used fastlane , sentry cli, dart flutter cli, and now we are using gradle. I think that is not a version problem... but i'm focused to solve it.

[scttcper]

I think this is usually why sourcemaps wouldn't work correctly. If that doesn't fix your issue, feel free to reopen this issue.

[lberaldodev]

Hey @scttcper my bad. Is this tag that you mentioned? :"D

[scttcper]

@lberaldodev yes does that release have the proguard mappings associated with it?

[lberaldodev]

yes, men! check the evidences ... the release version is the same of the error

[scttcper]

@lberaldodev can you share a link to the issue

[lberaldodev]

I can share the json issue, can be it?

[scttcper]

@lberaldodev opening a ticket with support would also allow us to debug further. Link to this issue as well if you do that.