uploadNativeSymbols and autoUploadNativeSymbols options behaviour
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 50/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- build-system, mobile-dev
Research direction
Start by tracing how the uploadNativeSymbols and autoUploadNativeSymbols options configure the uploadSentryNativeSymbolsForAppArm64Release task and the post-build execution. Compare assembleAppArm64Release with manually invoking the upload task, and confirm that conditional production versus nightly behavior matches the proposed option semantics.
Written by the indexing model from the issue text.
Description
Problem Statement
As I understood those options works as following:
uploadNativeSymbols option adds and configure a gradle task to upload symbols with --no-upload arg.
autoUploadNativeSymbols works as a switch for --no-upload, if auto is enabled, so --no-upload omitted.
This is not quite convenient for case when you want conditional upload: upload for production builds and ignore for nightly builds. Now I am using additional gradle parameter and define a function:
fun isUploadEnabled(): Boolean {
return project.hasProperty("uploadNativeSymbols") &&
project.property("uploadNativeSymbols").toString().toBoolean()
}
sentry {
uploadNativeSymbols.set(isUploadEnabled())
}
gradlew assembleAppReleaseArm64 -p uploadNativeSymbols
Solution Brainstorm
I suggest the following behaviour:
uploadNativeSymbols = true creates gradle tasks but not invoke the upload cmd. If I have to, I'll call it manually:
gradlew assembleAppArm64Release
gradlew uploadSentryNativeSymbolsForAppArm64Release
autoUploadNativeSymbols is responsible for automatic execution of uploadSentryNativeSymbols* task as post build step.
Sorry If I missed something.
Best Regards.
- Dominant language
- Kotlin
- Stars
- 184
- Forks
- 41
- Avg merge
- 1d 21h
- 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
-
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 Stale Waiting for: Community
Difficulty 4/5 3-5 days Newbie friendliness 45/100
getsentry/sentry-android-gradle-plugin#1406 · 3 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
-
AutoInstallState uses a process-global mutable singleton (project-isolation violation)May be free again @runningcode claimed this 62 days ago, and no pull request is open. OpenBug
getsentry/sentry-android-gradle-plugin#1351 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
All issues in getsentry/sentry-android-gradle-plugin
Similar issues
-
Meta request
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
keiyoushi/extensions-source#19500 ·
Maintainers usually reply within 1 day
-
go 🏃 testing 🧪
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
valkey-io/valkey-glide#7239 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
ethereum-lists/chains#8788 ·
Maintainers usually reply within 1 day
-
documentation P1
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
modelcontextprotocol/kotlin-sdk#1050 ·
Maintainers usually reply within 2 days