Skip to content

Commit

Permalink
Merge pull request #25 from livefront/prepare-for-v1.1.3-release
Browse files Browse the repository at this point in the history
Prepare for v1.1.3 release
  • Loading branch information
brian-livefront committed Oct 8, 2018
2 parents e04ddba + 3db5fc8 commit bd2554d
Show file tree
Hide file tree
Showing 2 changed files with 9 additions and 1 deletion.
6 changes: 6 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,12 @@
Change Log
==========

Version 1.1.3 *(2018-10-08)*
----------------------------
* `Bridge.clear` is now safe to call in `Activity.onDestroy` when "Don't Keep Activities" is enabled.
* All data is now correctly cleared on fresh launches for apps that do not use `Bridge` in every `Activity`.
* Min SDK is now 14.

Version 1.1.2 *(2018-06-04)*
----------------------------

Expand Down
4 changes: 3 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -65,6 +65,8 @@ Bridge.initialize(getApplicationContext(), new SavedStateHandler() {

That's it! You don't have to change any of your other code. If you are using any other `Icepick`-like library, simply swap out the library referred to in the `SavedStateHandler`.

Note that if you use the [Android-State](https://github.com/evernote/android-state) library as your `SavedStateHandler`, do **not** use the global settings by calling `StateSaver.setEnabledForAllActivitiesAndSupportFragments(this, true)`; failure to omit this will defeat the purpose of using `Bridge` and you will still see `TransactionTooLargeException` in your application.

<a name="clear"></a>
## Clearing Data

Expand Down Expand Up @@ -93,7 +95,7 @@ repositories {
}
dependencies {
compile 'com.github.livefront:bridge:v1.1.2'
compile 'com.github.livefront:bridge:v1.1.3'
}
```

Expand Down

0 comments on commit bd2554d

Please sign in to comment.