Platform:

• [x] Android, targetSdkVersion 30
• [x] Java
• [ ] Kotlin
• [ ] NDK
• [ ] React-Native

IDE:

• [x] Android Studio
• [ ] IntelliJ
• [ ] Other

The version of sentry-android: 2.3.0(at least) - master

I have the following issue:

When I set the targetSdkVersion to 30 for my app and launch it on an Android 11 device (my Pixel 4XL), the app crashes immediately.

Steps to reproduce:

1. Clone the sentry-android repository
2. Change the example app to use targetSdkVersion 30.

diff --git a/sentry-samples/sentry-samples-android/build.gradle.kts b/sentry-samples/sentry-samples-android/build.gradle.kts
index 5c29345..d299d1b 100644
--- a/sentry-samples/sentry-samples-android/build.gradle.kts
+++ b/sentry-samples/sentry-samples-android/build.gradle.kts
@@ -10,7 +10,7 @@ android {
     defaultConfig {
         applicationId = "io.sentry.samples.android"
         minSdkVersion(Config.Android.minSdkVersionNdk)
-        targetSdkVersion(Config.Android.targetSdkVersion)
+        targetSdkVersion(30)
         versionCode = 2
         versionName = "1.1.0"

3. launch sentry-samples-android

Actual result:

• Immediate crash

            libc  F  Pointer tag for 0x79f0abdc30 was truncated.
          Sentry  D  Processing dir. /data/user/0/io.sentry.samples.android/cache/sentry/sessions
            libc  F  Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 15999 (samples.android), pid 15999 (samples.android)
          Sentry  D  Processing 6 items from cache dir /data/user/0/io.sentry.samples.android/cache/sentry/sessions
                  D  Processing file: /data/user/0/io.sentry.samples.android/cache/sentry/sessions/f146b6e6-91af-4a2f-a08c-014613f5e594.envelope
                  D  Processing Envelope with 1 item(s)
                  D  Captured Envelope is already cached
                  D  Item 1 is being captured.
                  D  Going to wait flush 1 item.
TetheringManager  I  registerTetheringEventCallback:io.sentry.samples.android
           DEBUG  F  #00 pc 000000000004de4c  /apex/com.android.runtime/lib64/bionic/libc.so (abort+164) (BuildId: 03452a4a418e14ff93948f26561eace6)
                  F  getsentry/sentry-android#1 pc 000000000003bb34  /apex/com.android.runtime/lib64/bionic/libc.so (free+96) (BuildId: 03452a4a418e14ff93948f26561eace6)
                  F  getsentry/sentry-android#2 pc 00000000000781a8  /data/app/~~gQctd6Q5azmrHpqfGRaWvQ==/io.sentry.samples.android-IaNp2cunocnQXp3s03mjng==/lib/arm64/libsentry.so (sentry_f
                     ree+36) (BuildId: a8252e0bb65f23db1c6420f10a30b2f3b1477309)
                  F  getsentry/sentry-android#3 pc 0000000000085880  /data/app/~~gQctd6Q5azmrHpqfGRaWvQ==/io.sentry.samples.android-IaNp2cunocnQXp3s03mjng==/lib/arm64/libsentry.so (BuildId:
                      a8252e0bb65f23db1c6420f10a30b2f3b1477309)
                  F  getsentry/sentry-android#4 pc 0000000000085710  /data/app/~~gQctd6Q5azmrHpqfGRaWvQ==/io.sentry.samples.android-IaNp2cunocnQXp3s03mjng==/lib/arm64/libsentry.so (sentry_v
                     alue_decref+92) (BuildId: a8252e0bb65f23db1c6420f10a30b2f3b1477309)
                  F  getsentry/sentry-android#5 pc 000000000007f038  /data/app/~~gQctd6Q5azmrHpqfGRaWvQ==/io.sentry.samples.android-IaNp2cunocnQXp3s03mjng==/lib/arm64/libsentry.so (BuildId:
                      a8252e0bb65f23db1c6420f10a30b2f3b1477309)

Expected result:

• No crash

Project was working fine with sentry plugin before upgrade to AS 3.3 and the matching dev tools.

Now I have more build variants than just release/debug which I had before.

When I build a release version of the APK I get "Task :persistSentryProguardUuidsForReleaseArm64-v8a-release FAILED". The plugin is trying to run command:

"[user]\\AppData\\Local\\Temp\\.sentry-cli8452420388174734644.exe" "upload-proguard" "--android-manifest" "[project_root]\\build\\intermediates\\merged_manifests\\release\\AndroidManifest.xml" "--write-properties" "[project_root]\\build\\intermediates\\merged_assets\\release\\mergeReleaseAssets\\out/sentry-debug-meta.properties" "[project_root]\\build\\outputs\\mapping\\release\\mapping.txt"

but there is no "[project_root]\\build\\intermediates\\merged_manifests\\release\\AndroidManifest.xml", instead there is "[project_root]\\build\\intermediates\\merged_manifests\\release\\arm64-v8a\\AndroidManifest.xml". The task fails with "error: The system cannot find the file specified. (os error 2)".

I am running the build on Windows 10.

1. https://sentry.io/recharge/consumer-android/issues/293914847/ (using com.joshdholtz.sentry:sentry-android:1.6.0)
2. https://sentry.io/recharge/consumer-android/issues/293913146/ (using io.sentry:sentry-android:1.0.0)

Note that the message in #2 is a red herring, it's the wrapping exception's message which is almost never the useful one. #1 is correctly showing the root cause exception type/message.

[INFO] sentry_cli::api request POST https://sentry.io/api/0/projects/OrgName/ProjectName/files/dsyms/ [INFO] sentry_cli::api using token authentication [INFO] sentry_cli::api sending form data [INFO] sentry_cli::api > POST /api/0/projects/OrgName/ProjectName/files/dsyms/ HTTP/1.1 [INFO] sentry_cli::api > Host: sentry.io [INFO] sentry_cli::api > Accept: / [INFO] sentry_cli::api > Connection: TE [INFO] sentry_cli::api > TE: gzip [INFO] sentry_cli::api > User-Agent: sentry-cli/1.35.5 [INFO] sentry_cli::api > Authorization: Bearer a57d5458*** [INFO] sentry_cli::api > Content-Length: 228 [INFO] sentry_cli::api > Content-Type: multipart/form-data; boundary=------------------------b1d8f431c86402e9 [INFO] sentry_cli::api < HTTP/1.1 400 BAD REQUEST [INFO] sentry_cli::api < Server: nginx [INFO] sentry_cli::api < Date: Fri, 05 Oct 2018 23:32:07 GMT [INFO] sentry_cli::api < Content-Type: application/json [INFO] sentry_cli::api < Content-Length: 35 [INFO] sentry_cli::api < Connection: keep-alive [INFO] sentry_cli::api < X-XSS-Protection: 1; mode=block [INFO] sentry_cli::api < Content-Language: en [INFO] sentry_cli::api < X-Content-Type-Options: nosniff [INFO] sentry_cli::api < Vary: Accept-Language, Cookie [INFO] sentry_cli::api < Allow: GET, POST, HEAD, OPTIONS [INFO] sentry_cli::api < X-Frame-Options: deny [INFO] sentry_cli::api < X-Served-By: web-17b74f97 [INFO] sentry_cli::api < Strict-Transport-Security: max-age=31536000; includeSubDomains; preload [INFO] sentry_cli::api response: 400 [INFO] sentry_cli::api body: {"detail": "Missing uploaded file"} error: API request failed caused by: sentry reported an error: Missing uploaded file (http status: 400)

Properties file: log.level=debug defaults.project=ProjectName defaults.org=OrgName auth.token=Token

(values seem ok here, not sure what can or cant publish)

proguard file: -keepattributes LineNumberTable,SourceFile -dontwarn org.slf4j.** -dontwarn javax.** -keep class io.sentry.event.Event { *; }

Help plz.

Hello, I am using latest version 1.7.3 gradle plugin with gradle version 4.9. When I run assembleRelease task my build finishes successfully. However when my app crashes I still see obfuscated stack trace. How could I resolve this? Is there any way that I could view my uploaded mappings.txt file or at least verify that it's really there? Logs:

> Task :app:persistSentryProguardUuidsForReleaseRelease
> compressing mappings
> uploading mappings
> Uploaded a total of 1 new mapping files
Newly uploaded debug symbols:
 4fcc9d17-473e-5bd5-b61b-f51608f43daf

Using version 1.7.16 of sentry-android-gradle-plugin, after a gradle sync, this warning appears:

WARNING: API 'variant.getMergeAssets()' is obsolete and has been replaced with 'variant.getMergeAssetsProvider()'.
It will be removed at the end of 2019.
For more information, see https://d.android.com/r/tools/task-configuration-avoidance.
To determine what is calling variant.getMergeAssets(), use -Pandroid.debug.obsoleteApi=true on the command line to display a stack trace.
Affected Modules: app

Just taking public notes here. The work will actually span multiple repos.

My understanding is we need (roughly):

• A way for users to upload the Proguard mapping files when they do a release (part of sentry-cli, and a Gradle plugin that uses it)
• Support for Proguard processing in Sentry, which was started here but has been blocked while some reprocessing PRs were finished

I'm not sure what else is necessary yet. Proguard is nice in that the mapping files are generated locally when you do a build, so I don't think we need to do any of the difficult stuff we do for iOS as far as chasing down symbol files on someone else's server...

@mitsuhiko is the real expert on Sentry (re-)processing and mobile so maybe he can chime in here.

Overview

Typically, crash reporters will persist crash data in the event it doesn't get sent immediately, e.g. sending crash events the next time a process is run. raven-java doesn't appear to persist the data anywhere, so uncaught exceptions cannot be reported.

Steps to reproduce

1. Add raven-java to an Android project
2. Call Raven.sendException inside Java's uncaught exception handler*
3. Raise a RuntimeException (or other exception) outside of a try/catch block

* For example:

Thread.getDefaultUncaughtExceptionHandler();
Thread.setDefaultUncaughtExceptionHandler(new Thread.UncaughtExceptionHandler() {
  public void uncaughtException(Thread t, Throwable e) {
    Log.e("An uncaught exception occurred: " + e);
    Raven.sendException(e);
  }
});

Expected results

Log is emitted immediately, and an event is sent to Sentry the next time the app is run.

Actual results

Log is immediately sent, but the Sentry Event is never sent due to the app being terminated before transmission completes. Is there another way to configure Sentry that I'm missing?

Proposed solution

Store events in the circular FIFO queue prior to transmission. Remove them as they are sent, but in the event of an uncaught exception, serialize the queue to some configured path on disk. When Raven is initialized, it should attempt to restore the queue from data on disk at the configured location.

When you have multiple flavors/dimensions in the project, the sentry.properties file does not work when it is placed in a folder with a combination of flavors from different dimensions.

CC: @justacodefan

new spring boot starter module was added in #636. This is relying in spring boot 1.5.x release. My question is how sentry should be configured for apps who do not rely in servlet implementations I mean reactive apps.

I try to use Sentry for the first time, i tried some basic exceptions errors but i cant see them on my project in Sentry. I get this error: io.sentry.connection.AsyncConnection : An exception occurred while sending the event to Sentry.

and that is my simple code: package com.springBoot.springboot;

import java.util.Arrays; import org.springframework.boot.CommandLineRunner; import org.springframework.boot.SpringApplication; import org.springframework.boot.autoconfigure.SpringBootApplication; import org.springframework.context.ApplicationContext; import org.springframework.context.annotation.Bean;

import io.sentry.Sentry;

@SpringBootApplication public class Application {

@Bean
public CommandLineRunner commandLineRunner(ApplicationContext ctx) {
	return args -> {
		Sentry.init("https://fbc0bfe9a3a24bb09dce61166386f8d8:[email protected]/233687");

		try {
			int[] arr = {1 , 2 , 3};
			arr[4] = 10;
			 System.out.println("Hello World");
			
		} catch (Exception e) {
			Sentry.capture(e);
		}
	};
}
public static void main(String[] args) {
	SpringApplication.run(Application.class, args);
}

}

any help? Thanks

Bumps actions/setup-java from 2 to 3.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Bumps actions/checkout from 2 to 3.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

:scroll: Description

Added list of MemoryCollectionData to Android profiles payload as measurements

:bulb: Motivation and Context

We want to add more data to profiles, so we are including the memory statistics we get from transactions to profile payloads. Also, at the moment there's no easy way to send the data in the transaction, due to transaction metrics not supporting lists of data. We want to have some data and eventually show it in the Sentry dashboard. The quickest way is to send them in the profiles.

:green_heart: How did you test it?

Unit tests

:pencil: Checklist

• [X] I reviewed the submitted code
• [X] I added tests to verify the changes
• [ ] I updated the docs if needed
• [X] No breaking changes

:crystal_ball: Next steps

We still need to align on the keys and units used in the profile measurements with cocoa and relay Also, I need to understand if we have to change the timestamp logic of memory usages, as profiles measurements requires nanoseconds relative to the profile start

Description

We should avoid setting tags when possible.

See meta issue for more details: https://github.com/getsentry/team-mobile/issues/60

I just checked Java/Android usage:

Any tags set via SentryOptions.addContextTag() - but since they're custom values and empty by default I guess we can ignore those setTag("TimberTag", ...) -> link setSideLoadedInfo(...) -> link

:scroll: Description

Add an event processor which captures the View Hierarchy.

:bulb: Motivation and Context

https://github.com/getsentry/team-mobile/issues/64

Some refactoring was required: Created at CurrentActivityIntegration which watches for activity lifecycle updates and updates the CurrentActivityHolder singleton - this was previously managed by the ScreenshotEventProcessor. Now both ScreenshotEventProcessor and ViewHierarchyEventProcessor use the CurrentActivityHolder to retrieve the current activity.

Open issues:

• [ ] https://github.com/getsentry/relay/issues/1704 needs fixed first before we can use the proper attachment_type

:green_heart: How did you test it?

Unit tests

:pencil: Checklist

• [X] I reviewed the submitted code
• [X] I added tests to verify the changes
• [ ] I updated the docs if needed
• [X] No breaking changes

:crystal_ball: Next steps

:scroll: Description

added ttfd span added a FullyDrawnReporter instance to SentryAndroid added a new api SentryAndroid.reportFullyDrawn()

:bulb: Motivation and Context

We want to allow the user to report when the ui is fully loaded for them, e.g. after retrieving some data from some api call and fill their own ui

:green_heart: How did you test it?

Unit tests

:pencil: Checklist

• [ ] I reviewed the submitted code
• [ ] I added tests to verify the changes
• [ ] I updated the docs if needed
• [ ] No breaking changes

:crystal_ball: Next steps

I have to add a unit test for SentryAndroid.reportFullyDrawn() An rfc has to be submitted about the new api