Skip to content

Releases: livefront/bridge

2.0.2

Choose a tag to compare

@byencho byencho released this 19 Apr 16:15
cb8299a
  • Ensured that malformed or incomplete data saved to disk does not result in an exception when attempting to restore state.

2.0.1

Choose a tag to compare

@byencho byencho released this 31 Mar 21:59
76daf61
  • Improved thread-safety to avoid rare NullPointerException.

2.0.0

Choose a tag to compare

@byencho byencho released this 16 Mar 20:50
d3d09b2
  • Bridge now depends on AndroidX rather than the support libraries.

1.3.1

Choose a tag to compare

@byencho byencho released this 02 Mar 20:11
15a55e6
  • Prevented CancellationException that might result due to a rare race condition on startup.

1.3.0

Choose a tag to compare

@byencho byencho released this 07 Dec 15:03
6cceded
  • Reduced memory usage when processing data by skipping Base64-encoding step and using custom file storage.
  • Improved performance when processing Bitmap objects by avoiding compression.

1.2.1

Choose a tag to compare

@byencho byencho released this 14 Nov 22:27
b38e640
  • Fixed bug preventing data from being properly cleared internally during configuration changes.
  • Fixed bug resulting in non-launcher intents (such as deep links) sometimes unnecessarily clearing saved data.

1.2.0

Choose a tag to compare

@byencho byencho released this 30 May 21:53
85c00a3
  • Bridge can now save the state of View objects. You may now optionally provide a ViewSavedStateHandler to Bridge.initialize in order to unlock this functionality.
  • Improved performance during configuration changes and when navigating while apps are in the foreground.

1.1.3

Choose a tag to compare

@byencho byencho released this 08 Oct 13:45
bd2554d
  • 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.

1.1.2

Choose a tag to compare

@byencho byencho released this 04 Jun 14:31
58f8b55

Data will no longer be automatically cleared for objects that go out of memory while an app is running. It is now more strongly recommended to use the clear method to manually delete data for objects in the process of being discarded.

1.1.1

Choose a tag to compare

@byencho byencho released this 17 Aug 15:43
  • Fixed clear behavior for a removed Fragment in the backstack.