You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,17 @@
1
1
# Changelog
2
2
3
+
## 7.0.0 (2022-05-30)
4
+
5
+
This version contains **breaking** changes: some errors generated by the new version will no longer group in the Bugnsag dashboard with equivalent errors generated by older versions. This is due to the introduction of a new exception interceptor that gets passed the C# exception objects, rather than having to parse the information from Unity logs.
6
+
7
+
Please see the [upgrade guide](./UPGRADING.md) for details of all the changes and instructions on how to upgrade.
8
+
9
+
### Dependency updates
10
+
11
+
* Update bugsnag-android from v5.22.0 to [v5.22.4](https://github.com/bugsnag/bugsnag-android/blob/master/CHANGELOG.md#5224-2022-05-24)
12
+
13
+
* Update bugsnag-cocoa from v6.16.1 to [v6.17.1](https://github.com/bugsnag/bugsnag-cocoa/blob/master/CHANGELOG.md#6171-2022-05-18)
Copy file name to clipboardExpand all lines: UPGRADING.md
+19Lines changed: 19 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,25 @@
1
1
Upgrading
2
2
=========
3
3
4
+
## 6.x to 7.x
5
+
6
+
When building using Unity 2019+, the Bugsnag SDK now uses a new method to intercept uncaught C# exceptions. This allows us access to the original exception object, meaning more accurate exception data and full support for inner exceptions.
7
+
8
+
This has slightly changed the format used for method names and signatures, which means that uncaught C# exceptions reported by `bugsnag-unity` V7+ will not group automatically in the Bugsnag dashboard with the equivalent exception reported by older versions of the library.
9
+
10
+
The impact of this will be that some errors will effectively be duplicated between older and newer versions of your app.
11
+
12
+
Handled errors and native crashes will maintain their existing groups and are not affected by this upgrade.
13
+
14
+
#### Deprecation summary
15
+
16
+
The following methods have been removed from the `Bugsnag` client:
17
+
18
+
`Bugsnag.SessionTracking;` Please see the [capturing sessions](https://docs.bugsnag.com/platforms/unity/capturing-sessions/) section of our documentation for details on working with sessions.
0 commit comments