Support multi-module Android projects when sending Source Context
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- build-system, mobile
Research direction
Start with the minimal reproduction project linked in the issue and inspect how the Sentry Gradle Plugin handles additionalSourceDirsForSourceContext. Run assembleRelease and compare the generated source context with the expected classes from both x and y modules; done means the bundle includes classes from both modules without requiring manual configuration.
Written by the indexing model from the issue text.
Description
Problem Statement
When sending Source Context via Sentry Gradle Plugin, I've noticed that the source is taken only from the main application module. This is problematic for multi-module setups, which are fairly common.
I've prepared a minimal reproduction project of what I have in mind.
Reproduction
An Android application with x app module and y its dependency: https://github.com/wzieba/SentrySourceContextMultiModule
Expected behavior
Running assembleRelease prepares source context bundle with all classes from x and all classes from y modules.
Current behavior
Running assembleRelease prepares source context bundle with only classes from x (proof: https://github.com/wzieba/SentrySourceContextMultiModule/actions/runs/8467510900/job/23198486580#step:5:20)
Solution Brainstorm
I think it could be addressed manually with additionalSourceDirsForSourceContext, but I haven't prepared a working solution yet. Ideally, It'd be great if SAGP could do this internally (maybe as a non-default option?).
- Dominant language
- Kotlin
- Stars
- 184
- Forks
- 41
- Avg merge
- 2d 10m
- Merged PRs (30d)
- 20
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from getsentry/sentry-android-gradle-plugin
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
getsentry/sentry-android-gradle-plugin#1454 · 1 comment ·
Maintainers usually reply within 1 day
-
Android Improvement
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
getsentry/sentry-android-gradle-plugin#1369 · 1 comment ·
Maintainers usually reply within 1 day
-
Android good first issue Improvement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
getsentry/sentry-android-gradle-plugin#1266 · 1 comment ·
Maintainers usually reply within 1 day
-
Android Feature Waiting for: Community
Difficulty 4/5 3-5 days Newbie friendliness 45/100
getsentry/sentry-android-gradle-plugin#1406 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
Task
Difficulty 4/5 3-5 days Newbie friendliness 45/100
getsentry/sentry-android-gradle-plugin#1354 · 1 comment ·
Maintainers usually reply within 1 day
All issues in getsentry/sentry-android-gradle-plugin
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
AAswordman/Operit#1292 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
bug webview
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
home-assistant/android#7524 ·
Maintainers usually reply within 1 day
-
Issue: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
OpenAPITools/openapi-generator#25021 ·
Maintainers usually reply within 1 day