Replies: 2 comments 4 replies
-
|
I believe @Digifais had done some work towards Firebase 11, but I'm not sure where that is right now. Updating the Firebase suite over a major version is just a lot more effort than minor version bumps. In the case of a minor version update, the effort needed to published a new set of bindings is usually just bumping dependency versions. It's not usually necessary to write bindings for any new native APIs that might have been exposed. A major version bump is a signal that breaking changes have been made, so we need to be a lot more careful. Whole XCFramework dependencies might have been added or removed. Header files should be diffed to check for breaking API changes, and bindings need to be updated if any are found. I recommend starting with 11.0 so that effort can be focused on the minimum changes needed to get through the major version, and then incrementally working up to 11.4. It's a bit easier to tackle these upgrades one bite at a time, and it's nice to have a published nuget for each version. Its rare, but sometimes bugs make it into the native libraries and it can be nice to have the option to downgrade to the last working version. |
Beta Was this translation helpful? Give feedback.
-
|
@bengavin I just pushed nugets for MLKitBarcodeScanning v6. Please give them a try and let me know if they actually work 🙃 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Good morning!
I'm in the process of putting together a PR to update the MLKit.BarcodeScanning dependencies to MLKit 7 [Sept 2024 release]. It looks like I'm going to need to update some of the 'core' libraries to versions beyond what Firebase 10.x supports. Is there any plan to upgrade to the 11.5 release of Firebase, or was there a blocker discovered that prevents this before I start too far down this path? :)
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions