Lower compose version to avoid breaking change added in 1.7.0 #301
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
1.7.0 of
compose-runtime
(any compose-bom after2024.08.00
) has a breaking change in our snapshots SDK when targeting an app with 1.6.8 or lower (bom2024.08.00
).When building our SDK with a 1.7.0+, a
rememberComposableLambda
function is called that was added in 1.7.0. When our snapshots SDK is used as anandroidTestImplementation
dependency against an app with a lower compose version, this function is not present, which leads to aNoSuchMethodError
upon trying to invoke the snapshot.For now, this should be able to be fixed with a simple version drop, and longer term we can work through a more elegant solution that can allow us to ship with whatever version of compose we'd like, while supporting any client version.