Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ARCore in nanopb Dependency Conflict with Firebase & Flutter #104

Open
vilorel opened this issue Sep 5, 2024 · 3 comments
Open

ARCore in nanopb Dependency Conflict with Firebase & Flutter #104

vilorel opened this issue Sep 5, 2024 · 3 comments

Comments

@vilorel
Copy link

vilorel commented Sep 5, 2024

Hi all, we've built our AR module that relies on ARCore.
We're also using the Firebase Flutter packages and just tried to update them to the latest version.

The error we got is the following (when using Cocapods to build the dependency graph for iOS):

[!] CocoaPods could not find compatible versions for pod "nanopb": In Podfile: ar_flutter_plugin (from .symlinks/plugins/ar_flutter_plugin/ios`) was resolved to 0.6.2, which depends on
ARCore/CloudAnchors (~> 1.45.0) was resolved to 1.45.0, which depends on
nanopb (< 2.30911.0, >= 2.30908.0)

firebase_messaging (from `.symlinks/plugins/firebase_messaging/ios`) was resolved to 15.1.0, which depends on
  Firebase/Messaging (= 11.0.0) was resolved to 11.0.0, which depends on
    FirebaseMessaging (~> 11.0.0) was resolved to 11.0.0, which depends on
      nanopb (~> 3.30910.0)`

I understand that nanopb has breaking changes but when do you plan to launch support for the latest version? Otherwise I assume it's a big problem for Flutter users, potentially iOS too?

@naved997
Copy link

naved997 commented Sep 7, 2024

I have the same issue any solution for this?

@naved997
Copy link

naved997 commented Sep 7, 2024

Have you solution for this?

@vilorel
Copy link
Author

vilorel commented Sep 19, 2024

I rolled back all the upgrades for now and downgraded the firebase packages. Anything sort of Google supporting the new nanopb library would be a risky patch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants