Thank you @arnemolland
We'll have to wait for this to land at least on the beta channel, otherwise, it'd be breaking for people using the stable/beta channels.

It can be made backwards compatible as shown in #1166 (comment)

It can be made backwards compatible as shown in #1166 (comment)

Updated the PR, would you prefer not using the inner asset bundle?

Codecov Report

Patch coverage: 100.00% and project coverage change: +0.06 🎉

Comparison is base (d301b11) 89.76% compared to head (0b1a611) 89.83%.

@@            Coverage Diff             @@
##             main    #1272      +/-   ##
==========================================
+ Coverage   89.76%   89.83%   +0.06%     
==========================================
  Files         155      155              
  Lines        5032     5064      +32     
==========================================
+ Hits         4517     4549      +32     
  Misses        515      515              

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

Thanks! Added the suggested changes.

Fixed an issue with type argument not being implicitly forwarded to the dynamic (bundle as dynamic).loadStructuredBinaryData call and rebased on top of the latest changes. Let me know if anything is missing.

@arnemolland since this is possible using the override_on_non_overriding_member and it's not a breaking change any more.
Can you target the main branch instead? so we can release this with the current stable version.

@arnemolland since this is possible using the override_on_non_overriding_member and it's not a breaking change any more.
Can you target the main branch instead? so we can release this with the current stable version.

Sure thing, I'll rebase

There are some conflicts, search for <<<<<<< HEAD.
Also, the changelog should be under the Unreleased (v6)

There are some conflicts, search for <<<<<<< HEAD.
Also, the changelog should be under the Unreleased (v6)

Had to tidy up locally, should be good now.

@arnemolland there are 4 failing tests, mind checking out?

@arnemolland there are 4 failing tests, mind checking out?

Yes, seems to be related to tests running from stable trying to invoke the non-existing method, fixing that asap.

@arnemolland there are 4 failing tests, mind checking out?

Yes, seems to be related to tests running from stable trying to invoke the non-existing method, fixing that asap.

As expected, calling loadStructuredBinaryData on the inner bundle is no good for SDK versions <3.8. That wouldn't happen since it can't be called, but the test runner doesn't care since we're trying to call it directly instead of interfacing with an AssetBundle (as normal usage would be).

The quickest fix is to apply the second suggestion found here -- updating the PR.

My solution to the above problem was to refactor the code to emulate the AssetBundle's loadStructuredBinaryData implementation, so that we don't call the inner bundle and avoid the testing problem;

Future<T> _loadStructuredBinaryDataWrapper<T>(
    String key,
    FutureOr<T> Function(ByteData data) parser,
  ) async {
    final ByteData data = await load(key);
    return parser(data);
  }

This can be refactored back once the library drops backwards compatibility with Flutter < 3.8. LMK if this is an acceptable approach.

I don't think emulating is the way to go, as the loadStructuredBinaryData has quite a sophisticated implementation, which would be bypassed by emulating it. See https://master-api.flutter.dev/flutter/services/CachingAssetBundle/loadStructuredBinaryData.html
One particular drawback would be to basically remove the ability of the CachingAssetBundle to cache data for loadStructuredBinaryData.

Instead, you can adjust the TestAssetBundle and add loadStructuredBinaryData as a method just like in

Because the newly introduced method is then also available in all Flutter versions in the tests, every thing should be working.

I've done that in the past, see #877 as a reference how to do that.

I don't think emulating is the way to go, as the loadStructuredBinaryData has quite a sophisticated implementation, which would be bypassed by emulating it. See https://master-api.flutter.dev/flutter/services/CachingAssetBundle/loadStructuredBinaryData.html One particular drawback would be to basically remove the ability of the CachingAssetBundle to cache data for loadStructuredBinaryData.

Instead, you can adjust the TestAssetBundle and add loadStructuredBinaryData as a method just like in

sentry-dart/flutter/test/sentry_asset_bundle_test.dart

Lines 566 to 578 in 5e79e10

	@override
	// This is an override on Flutter greater than 3.1
	// ignore: override_on_non_overriding_member
	Future<ImmutableBuffer> loadBuffer(String key) async {
	if (throwException) {
	throw Exception('exception thrown for testing purposes');
	}
	if (key == _testFileName) {
	return ImmutableBuffer.fromUint8List(
	Uint8List.fromList(utf8.encode('Hello World!')));
	}
	return ImmutableBuffer.fromUint8List(Uint8List.fromList([]));
	}

Because the newly introduced method is then also available in all Flutter versions in the tests, every thing should be working.

I've done that in the past, see #877 as a reference how to do that.

Perfect, thanks!