Skip to content

Merge release branch into master #1428

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
Jul 22, 2019
Merged

Merge release branch into master #1428

Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
a1e16d4
Update CHANGELOG.md
vmutafov Jul 16, 2019
10a6ec4
Move 'Breaking Changes' section on the top
vmutafov Jul 17, 2019
3f29e57
Update CHANGELOG.md
vmutafov Jul 17, 2019
d8ec4e8
Merge pull request #1421 from NativeScript/vmutafov/update-changelog-…
Jul 17, 2019
3d4bd67
chore: Bump package version to 6.0.1
mbektchiev Jul 22, 2019
35d0338
Merge pull request #1427 from NativeScript/bektchiev/bump-rc-version
mbektchiev Jul 22, 2019
c5be5fb
Merge branch 'master' into vmutafov/merge-release-to-master
vmutafov Jul 22, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 12 additions & 9 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,8 +1,20 @@
6.0.0
==

## Breaking Changes

- Exception information in onDiscarderError and onUnhandledError is changed so that `message` contains the exception message and `stackTrace` contains only the stackTrace. In the previous implementation `stackTrace` contained some additional details (including the exception message) and the `message` was something like:

```
The application crashed because of an uncaught exception. You can look at "stackTrace" or "nativeException" for more detailed information about the exception.
```

- [The built-in `JSON.stringify` method is used for cross workers communication](https://github.com/NativeScript/android-runtime/issues/1408). Circular object references are no longer supported and attempting to send such object will throw an exception.


## What's New

- [Use the built-in JSON.stringify for cross workers communication (#1411)](https://github.com/NativeScript/android-runtime/pull/1411)
- [Enable AndroidX and Jetifier(#1370)](https://github.com/NativeScript/android-runtime/issues/1370)
- [Upgrade v8 to 7.5.288.22(#1387)](https://github.com/NativeScript/android-runtime/issues/1387)
- [Upgrade android gradle plugin to the latest 3.4.1 version(#1390)](https://github.com/NativeScript/android-runtime/issues/1390)
Expand All @@ -17,15 +29,6 @@
- [Warnings when building android(#1396)](https://github.com/NativeScript/android-runtime/issues/1396)
- [No JS stack on discardedError and unhandledError(#1354)](https://github.com/NativeScript/android-runtime/issues/1354)

## Breaking Changes

- Exception information in onDiscarderError and onUnhandledError is changed so that `message` contains the exception message and `stackTrace` contains only the stackTrace. In the previous implementation `stackTrace` contained some additional details (including the exception message) and the `message` was something like:

```
The application crashed because of an uncaught exception. You can look at "stackTrace" or "nativeException" for more detailed information about the exception.
```

- [The built-in `JSON.stringify` method is used for cross workers communication](https://github.com/NativeScript/android-runtime/issues/1408). Circular object references are no longer supported and attempting to send such object will throw an exception.

5.4.0
==
Expand Down