I would like macOS to be officially supported by Firebase.
I think this won't be a priority for a while. @salqadri can maybe talk more about it.
Hey Jack,
We actively encourage and assist the community in building and maintaining the macOS SDK. Could you tell us more on why it's important to you for macOS to be 'officially supported'?
A macOS app I am making requires Firebase Database, and an officially
supported version would be more stable.
On Dec 20, 2017 1:38 PM, "salqadri" notifications@github.com wrote:
Hey Jack,
We actively encourage and assist the community in building and maintaining
the macOS SDK. Could you tell us more on why it's important to you for
macOS to be 'officially supported'?ā
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/firebase/firebase-ios-sdk/issues/583#issuecomment-353146938,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWFWNBkNS23WiGFuom2upGMSTkqvxIV_ks5tCVQ0gaJpZM4RHgQS
.
@JackRichardBusiness Will you be more specific about where the community supported macOS SDK hasn't met your stability requirements? Any issues that you're seeing?
Closing since this isn't going to happen soon and this issue hasn't garnered much community support. We're revisiting this now.
Many of the components here compile and run on macOS (see here for more details), but Firebase doesn't provide official support for Firebase client SDK issues on macOS. You may still file issues you run into here and receive unofficial support.
@salqadri and @morganchen12 Could you provide a link to the community supported macos sdk please? Thanks!
For the reference of others, did you mean this? https://github.com/firebase/firebase-ios-sdk#macos
@joelgetaction This - https://github.com/firebase/firebase-ios-sdk#macos-and-tvos
Bump. There should be no reason this isn't usable for both platforms.
Can we add support for macOS via Carthage? Right now we only have this:
binary "https://dl.google.com/dl/firebase/ios/carthage/FirebaseAnalyticsBinary.json"
@rismay We'll investigate. In the meantime, if you want a binary framework version of a mac distribution, CocoaPods/Rome is an option.
Can we get support for this since Apple is launching cross platform support for iOS apps?
I agree with @eebean2. A lot of iPad apps will be ported coming month due to Apples new Catalyst project. One switch in Xcode will make your app into a macOS app. However, frameworks need to support macOS and the only one I got an issue with was Firebase SDK!
We're digesting all of the WWDC updates and will reassess the Firebase multi-platform official support story.
In the meantime, please file any specific issues you have with the current community macOS support.
Not to mention there's very little multi-platform solutions out there. Can't think of anything other than realm database. Having Firebase on macOS would be a game changer for all of us - we'd love to switch over to Firebase wholeheartedly if given the chance.
If you can include Firebase in an iPadOS app, wonāt it work if deployed on a Mac? Itāll be running on an iOS-built app, wonāt it?
If you can include Firebase in an iPadOS app, wonāt it work if deployed on a Mac? Itāll be running on an iOS-built app, wonāt it?
Unfortunately it is not working at the moment. It needs to be able to run on macOS
Even if it did work for Catalyst / iPadOS apps on macOS, we'd appreciate proper support for native macOS apps. Just please do it and get it done and over with so we can all enjoy cross platform deployment of Firebase in our apps.
Is it possible to include firebase for macOS (UIKit for Mac) via pod 'FirebaseCore' ? I tried to make a separate target and set it in its own CocoaPods target (platform :macos, '10.15'), but importing via "import FirebaseCore" just gives me an error:
No such module 'FirebaseCore'
Any ideas? Or is this way impossible?
So far Iāve had some luck getting support for macOS through Catalyst. Hereās what I did
In the same project that works on iOS, select the Mac checkbox
Ran pod install
Solved certificates issues with the gRPC by selecting the team as needed (Only needed if Firestore pod is installed)
Selected the Mac as the target and commented any code pertaining to UIWebView in the FIRAuth files (only needed if FIRAuth pod is installed)
Also removed āAssetsLibraryā -framework from the .xcconfigs using the find and replace feature
Selected the Mac as the target and commented any code pertaining to UIWebView in the FIRAuth files (only needed if FIRAuth pod is installed)
Any adverse effects on FIRAuth?
I haven't had any issues with FIRAuth. If your deployment target is greater than 7.0 you should be fine.
Hi folks,
I'm wondering, is FirebaseAnalytics support for macOS somewhere on Google's radar? Are there any ETA for this feature available for macOS apps?
This would be a huge improvement, especially because there used to be Fabric analytics, which is now migrating to Firebase, and analytics simply kicked off.
With regards.
Mac Catalyst build fails for me:
ld: in .../Pods/FirebaseAnalytics/Frameworks/FIRAnalyticsConnector.framework/FIRAnalyticsConnector(FIRConnectorUtils_d79571aba36a7d46e5c6ca87a6fec1c1.o),
building for Mac Catalyst, but linking in object file built for iOS Simulator, file
.../Pods/FirebaseAnalytics/Frameworks/FIRAnalyticsConnector.framework/FIRAnalyticsConnector'
for architecture x86_64
when including Firebase Analytics:
pod 'Firebase/Analytics'
As documented at https://github.com/firebase/firebase-ios-sdk#tvos-macos-and-catalyst, we do not currently support Analytics for Catalyst (#4563)
Looking for a workaround, how can I still use Analytics on iOS and exclude it for the Catalyst build
@paulz See https://github.com/firebase/firebase-ios-sdk/issues/4563#issuecomment-573281457
That workaround didn't work for me.
Deadline for Fabricās demise is round the corner and we still donāt have proper macOS support. We heavily rely on analytics for our Mac apps and thatās all going away soon. If fabric can do it, how difficult is it to get it ready for Firebase? Not to mention Iām already annoyed Firebase requires a lot more clicks for what was easy to get to in Fabric.
I think official and ongoing support for macOS is a lost cause. Iāve liked Microsoft App Center as a replacement for crash logging and analytics. Itās worth checking out: https://appcenter.ms
@cliftonlabrum thanks for that, didnāt realize there was an alternative! What a shame. Google keeps emailing us threats that Fabric is discontinuing and at the same time hasnāt given us something to port to. I prefer keeping everything under the same portal so will move all the iOS + Android + macOS apps to Microsoft now.
@paulb777 can we at least have an official statement on why macOS support for analytics / performance and Firebase database is being delayed? Why do you guys keep asking why official support is needed. Isnāt it obvious? Analytics arenāt available. Thatās 50% of what crashlytics used to offer.
Surely someone clicks on the āSendā button for all these āFabrics is shutting downā emails we keep receiving. Ironically it asks us to migrate to Firebase, which does not support macOS apps. Why acquire a service and then ālameā it down? Google should have left fabric alone.
I had to create a git branch for my Catalyst and iOS project with the Analytics pod commented out on the catalyst branch. I tried creating multiple targets with the analytics pod only in the iOS target, but couldn't deploy to the app store because of a duplicated library problem. Thanks for the Microsoft tip. I will check it out.
Iāve received a response from Google Developer support that Firebase will not support analytics for macOS anytime soon. Okay Iām out of here.
Looking for a workaround, how can I still use Analytics on iOS and exclude it for the Catalyst build
I got this working:
https://stackoverflow.com/a/60213321/211457
@andytriboletti nice!! Sick timing to just come back - will test it out
Hi everyone. This is Shobhit, Product Manager for Crashlytics. Thank you for the feedback.
Firebase does not officially support Catalyst, macOS, and tvOS apps. If you are using Fabric Crashlytics with macOS and tvOS apps, you can migrate these apps to Firebase as iOS apps. If you have an iOS app with the same bundle ID that already exists in Firebase, then you will have to create your macOS/tvOS app in a separate Firebase Project.
The Crashlytics SDK will continue to report crashes for Catalyst, macOS, and tvOS apps. However, features that depend on Google Analytics or other Firebase products (i.e., Crash-Free Users, Velocity Alerts, and breadcrumbs) will not work for these apps.
We have no timeline for adding Firebase support for macOS and tvOS at this time but are continually evaluating platforms and will keep it on our radar.
@shobhitchugh I hope you appreciate this is extremely frustrating for all of us. Analytics works just fine within Fabric, yet we're being forced out of it to embrace a broken platform, that does not support Analytics, Events and and fails to report simple things such as "Launch Status for build xxx" ā something that was incredibly useful in Crashlytics (Fabric). One click and you can see the growing number of users / crashes. Not only is there no macOS support for this in Firebase, even the iOS version of Analytics does not provide us with this simple stat (I know "Latest release" does a lot more - exactly, it does a lot MORE and it's annoyingly slow and frustrating to use).
If google, with all its resources, cannot completely support an already working system, it should have left it alone. I realize the need to deprecate Fabric and the switch to Firebase, but why not keep it around for longer, especially macOS apps? We're going to be crippled once it's turned off after 31st March.
We are adding macOS support as we need it for our new launch but we will have to abandon firebase which is a shame as we've been customers of it for many many year
@jcampbell05 Sorry to hear that.
Is the issue that the support is not "official" or that the "community" support is missing features that you need?
@paulb777 I don't think anyone would really care if it were "official" as long as we all got what we've been asking for, for years? And that primarily is: "Analytics" support for macOS. We should be able to see "Analytic Events" as we do for our iOS apps. This feature works just fine in Fabric and I don't understand how or why it's difficult to port this over to Firebase. If there are technical hurdles, why not keep Fabric running and supporting macOS apps only till "official" support arrives in the year 3020 - oh wait, by then it wouldn't matter since those of us on this thread won't be alive.
We want Analytics to work for macOS. We want to be able to see the number of users using the app, other than just crash reports. We want to be able to see all the custom events we already are able to track in Fabric, for macOS.
@guidedways I'm familiar with the reasons for Analytics macOS support. However, @jcampbell05 said that they'd been Firebase customers for many years - which wouldn't apply to the Fabric migration reason for Analytics - since Crashlytics is a relatively recent addition to Firebase.
Let's have the Analytics specific discussion in #1732 and leave this issue for discussion around converting the existing Firebase community support for macOS to official support (which I understand is dependent upon the more specific #1732).
Is the issue that the support is not "official" or that the "community" support is missing features that you need?
I'm a long time user of Fabric and Firebase to clarify.
Community support would be better than nothing if it mean't we get the analytics features from Fabric/Google Analytics as well as GCM support.
But ultimately we would need some sort of official support as we don't want to be relying on an SDK that is only being supported by people in their spare time.
We're looking into adding a desktop companion to our iOS app so adding officially supported port for catalyst would be great.
Luckily all of the code here is open-source so if push comes to shove we can do it ourselves but then the issue is since there isn't "official" support - will the Firebase dashboard work well with this or does it assume all apps are either mobile or web and not catalyst.
For this application we would have to look in the longer term for cross-platform solutions.
I'm aware one blocker is you are waiting on some cocoa pods support but that may be a long time coming - instead I would suggest you do as Stripe are doing and release a Xcframework on GitHub releases.
We would be happy to use that for the time being instead of via Cocoapods if it mean't we can use the framework everywhere we need.
Let's have the Analytics specific discussion in #1732 and leave this issue for discussion around converting the existing Firebase community support for macOS to official support (which I understand is dependent upon the more specific #1732).
@paulb777 Fair enough. In that case, yes, we would (all?) like macOS to be officially supported by Firebase Crashlytics / Answers / Analytics etc - please š
@jcampbell05 Probably worth leaving a +1 under #1732, too
Please upvote the issue instead of leaving +1 comments which send a notification to everyone subscribed. Thanks!
@dtnam1997 I'm deleting your post above since it is cluttering a popular issue in the wrong repo. Please follow it at https://github.com/firebase/firebase-cpp-sdk/issues/50
I am building a macOS standalone process, a command line tool binary (non UI app). I am trying to integrate crashlytics into it. I manage to fix all other issues with bundle identifier, fetching dsym files and uploading etc.
The crash reports are getting uploaded to firebase console as per network proxy logs. I can see 202 Accepted status for POST requests to https://reports.crashlytics.com domain calls.
But I am not seeing any reports in firebase console.
Note: I also have another app under same project which is an UI based macOS app (.app like iOS). For this app the crash reports are displayed perfectly in the dashboard. Only for command line binaries it does not show up in the console dashboard.
Please help. Hope this issue adds to demand of official support of macOS apps and binaries.
Most helpful comment
@shobhitchugh I hope you appreciate this is extremely frustrating for all of us. Analytics works just fine within Fabric, yet we're being forced out of it to embrace a broken platform, that does not support Analytics, Events and and fails to report simple things such as "Launch Status for build xxx" ā something that was incredibly useful in Crashlytics (Fabric). One click and you can see the growing number of users / crashes. Not only is there no macOS support for this in Firebase, even the iOS version of Analytics does not provide us with this simple stat (I know "Latest release" does a lot more - exactly, it does a lot MORE and it's annoyingly slow and frustrating to use).
If google, with all its resources, cannot completely support an already working system, it should have left it alone. I realize the need to deprecate Fabric and the switch to Firebase, but why not keep it around for longer, especially macOS apps? We're going to be crippled once it's turned off after 31st March.