@herrernst This is something we are interested in doing, but unfortunately we currently cannot for various reasons. I can't give a timeline on this, unfortunately!

What's the main desire to see it open-sourced from your end? Just curious. Thanks for the FR!

Thanks for your answer.

What's the main desire to see it open-sourced from your end?

The generic reasons why to prefer open source over closed source: trust (I would like to see the code I include in my app to know what it does) and potential better debugging when there would be a problem.
I can live with it for now, only hope that the old 1.0.9 version of FirebaseInstanceID will not stop working anytime soon ;-) (One problem could arise when Apple introduces a new architecture.)

Thanks for the response @herrernst! Your reasons make perfect sense, and that's why we've been open-sourcing our SDKs. The InstanceID SDK will have newer versions that will continue to work, though it will remain closed-source for now. The locking of the version to 1.0.9 was temporarily, will be fixed soon.

Hello, I am currently porting Messaging on macOS. Since Messaging is using FirebaseInstanceID, and is currently only available for iOS, it could be nice to make it open source so we can use it also for macOS. If open source is not possible, maybe source code is already macOS compatible and only pod spec must be updated including osx support. Best.

Any update on this? FirebaseInstanceID 2.0.3 removed the dependency on FirebaseCore, but 2.0.8 added it again. Any reason why?

FirebaseInstanceID added dependencies to FirebaseCore for logging.

It's still the plan to open source FirebaseInstanceID but I can't give an update on timing.

how dose FirebaseInstanceID get user's local timezone? We deliver FCM message to users in local timezone on firebase console, but some of users receive notification at a wrong timezone. @paulb777

InstanceID use the [NSTimeZone localTimeZone] to get local timezone.

got it. Thanks

Thanks for your effort! But when installing Firebase 5.18.0 with (the now open source) FirebaseInstanceID 3.6.0 via CocoaPods, I still get the precompiled framework binary without source (in contrast to e.g. FirebaseCore or FirebaseMessaging, where I get lots of *.m files). Am I expecting something wrong?

@herrernst Thanks for the report! We've reproduced and discovered a glitch in the release process and are hoping to get the right version out ASAP.

@paulb777 Thank you!

FirebaseInstanceID 3.7.0 is now available. Thanks @herrernst for the report!

You may need to run pod deintegrate or rm -rf Pods before running pod update.

@paulb777 Thanks again. Source is now installed. Unfortunately, I have another problem. Something is broken when having "use_frameworks!" in the Podfile, my app crashes with "+[FIRInstanceIDCheckinPreferences preferencesFromKeychainContents:]: unrecognized selector sent to class 0x10f92f998".

It's reproducible in a fresh project:

• Create new Objective-C Single View App, close project
• pod init, add "pod 'FirebaseMessaging'" and uncomment "use_frameworks!", execute pod install
• Open workspace, add suitable GoogleService-Info.plist
• In app delegate:

#import <FirebaseCore/FirebaseCore.h>
#import <FirebaseMessaging/FirebaseMessaging.h>

and

- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
    [FIRApp configure];
    NSLog(@"token: %@", [FIRMessaging messaging].APNSToken); // needed to trigger crash
    return YES;
}

@herrernst I'm not able to reproduce. Maybe there is some stale build state? Are you able to see the crash in the Xcode debugger?

I've cleaned the project, still:

Example project attached.
TestFirebaseBuild.zip

@herrernst The unrecognized selector issue doesn't reproduce with CocoaPods 1.6.1. I reproduced it with CocoaPods 1.5.3 and worked around it there by adding -ObjC to the Other Linker Flags Build Setting.

@paulb777 Thanks for your help, after upgrading CocoaPods it's working now!!