Open timothyrobb opened 2 months ago
It looks like this has been fixed in RollbarNotifier 3.3.2 https://github.com/rollbar/rollbar-apple/issues/348#issuecomment-2293887391
Hi, Any guide on how to fix this issue??
Same issue as @timothyrobb here. App stop building after update to XCode 18.
I've checked the code here and the version 1.5.0 still pointing to the old RollbarNotifier version
It's been 14 months since the rollbar team updated pub.dev... that's a long time between platform versions:
I noticed some fixes on repo, and since this is technically still in beta, I'm targeting the repo directly in my pubspec.yml
dependencies:
...
rollbar_flutter:
git:
url: https://github.com/rollbar/rollbar-flutter.git
ref: main
path: rollbar_flutter/
...
Can we push this change, or anyone forked it yet?
and ... shit.
from readme.
As of April 2024, Rollbar will not be actively updating this repository and plans to archive it. We encourage our community to fork this repo if you wish to continue its development. While Rollbar will no longer be engaging in active development, we remain committed to reviewing and merging pull requests, particularly those about security updates. If an actively maintained fork emerges, please let us know, and we will gladly link to it from our documentation.
if anyone needs a fork, i updated code to handle RollbarNotifier and fixed the AndroidManifest.xml packageName/namespace issue for Android 15.
https://github.com/sonjz/rollbar-flutter/commit/265e9c9a49873e928a21c705660766d49cfdbbbc
add it to your pubspec.yaml
with:
...
dependencies:
...
rollbar_flutter:
git:
url: https://github.com/sonjz/rollbar-flutter.git
ref: main
path: rollbar_flutter/
...
Hope this helps as a stopgap, but yup, project is dead... Crashalytics anyone?
Using the latest released version of Xcode, v18, and using the latest version of
rollbar_flutter
, v1.5.0, we get compiler errors.This makes the package and service entirely unusable for any project that uses the latest version of Xcode.
I know this package is barely maintained, if ever. But if this isn't patched shortly, you're going to find almost every user of this package disappearing over a few months and using another service entirely.