-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #18858 from ndesai-newrelic/develop
docs:Troubleshoot and release note
- Loading branch information
Showing
3 changed files
with
43 additions
and
0 deletions.
There are no files selected for viewing
28 changes: 28 additions & 0 deletions
28
...bile-monitoring/new-relic-mobile-android/troubleshoot/no-crash-data-appears.mdx
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,28 @@ | ||
--- | ||
title: No crash data appears in release build (Android) | ||
type: troubleshooting | ||
metaDescription: 'Troubleshooting tips if no crash data appears in the mobile monitoring UI after you install, configure, and generate traffic for your Android app.' | ||
freshnessValidatedDate: 2024-10-04 | ||
--- | ||
|
||
## Problem [#problem] | ||
After an app crash, no crash data appears in the New Relic UI. You may see logs indicating that the agent is unable to find the `buildId`, which is required for crashes to be processed on the New Relic side. | ||
|
||
Here are console agent log messages that verify the issue: | ||
|
||
* `Agent.getBuildId() was unable to find a valid build Id. Crashes and handled exceptions will not be accepted.` | ||
* `Invalid null or empty build ID detected! Crash will be ignored by collector.` | ||
* `ExceptionHelper: java.util.UUID:fromStringJava8(UUID.java:337) RandomUUID[java.lang.IllegalArgumentException] Invalid UUID string:` | ||
* `Unable to get obfuscated flag in crash` | ||
|
||
## Solution [#solution] | ||
If you are using Android agent 7.x.x or higher and no crash data appears after an app crash, please follow these steps: | ||
|
||
1. Ensure you're using these Gradle and AGP versions: | ||
|
||
* Gradle version 7.5 or higher | ||
* AGP (Android Gradle Plugin) version 7.4.2 or higher | ||
|
||
2. Configure ProGuard rules: Double-check that proper ProGuard rules are added to your ProGuard configuration file. Refer to the [Configuring ProGuard Rules](/docs/mobile-monitoring/new-relic-mobile-android/install-configure/configure-proguard-or-dexguard-android-apps/) section in the setup documentation for guidance. | ||
|
||
If you need additional help, get support at [support.newrelic.com](https://.newrelic.com). |
13 changes: 13 additions & 0 deletions
13
...docs/release-notes/mobile-release-notes/unity-release-notes/unity-agent-141.mdx
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,13 @@ | ||
--- | ||
subject: Unity agent | ||
releaseDate: '2024-09-30' | ||
version: 1.4.1 | ||
downloadLink: 'https://github.com/newrelic/newrelic-unity-agent.git' | ||
--- | ||
|
||
|
||
## Improvements | ||
|
||
- Native Android agent updated to version 7.6.0 | ||
- Native iOS agent updated to version 7.5.2 | ||
- Bug fixes for Log Attributes method |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters