google-oss-bot
commented
2 years ago I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
Open SchwartzLizer opened 2 years ago
google-oss-bot
commented
2 years ago I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
ryanwilson
commented
2 years ago Sorry for the troubles @SchwartzLizer - I'm not sure why it's not logging. In the meantime, you can use the Installations API directly to grab it.
Installations.installations().installationID { identifier, error in
guard let installationID = identifier else {
print("Error getting installation ID: \(error!)")
}
print("Firebase installations ID = \(installationID)")
}
SchwartzLizer
commented
2 years ago Sorry for the troubles @SchwartzLizer - I'm not sure why it's not logging. In the meantime, you can use the Installations API directly to grab it.
Installations.installations().installationID { identifier, error in guard let installationID = identifier else { print("Error getting installation ID: \(error!)") } print("Firebase installations ID = \(installationID)") }
It work but now i have new problem when i get installationID and paste in firebase and send to test device but not show anything. I'm Looking in console like this
[Firebase/InAppMessaging][I-IAM180017] Seeing test message in fetch response. Turn the current instance into a testing instance.but not found
Console Log
8.13.0 - [Firebase/InAppMessagingDisplay][I-FID100010] Got notification for kFIRAppReadyToConfigureSDKNotification. Setting display component on headless SDK.
8.13.0 - [Firebase/InAppMessaging][I-IAM290001] Setting a non-nil message display component
8.13.0 - [Firebase/InAppMessaging][I-IAM170001] Got notification for kFIRAppReadyToConfigureSDKNotification
8.13.0 - [Firebase/InAppMessaging][I-IAM170002] Auto bootstrap Firebase in-app messaging SDK
8.13.0 - [Firebase/InAppMessaging][I-IAM170005] Not running in simulator. Use regular clearcut uploading strategy.
8.13.0 - [Firebase/InAppMessaging][I-IAM310001] Persistent file path for activity log data is /var/mobile/Containers/Data/Application/5BA94567-81A6-46ED-A1AC-696EFA9B729A/Library/Caches/firebase-iam-activity-log-cache
8.13.0 - [Firebase/InAppMessaging][I-IAM230001] Persistent file path for clearcut log records is /var/mobile/Containers/Data/Application/5BA94567-81A6-46ED-A1AC-696EFA9B729A/Library/Caches/firebase-iam-clearcut-retry-records
8.13.0 - [Firebase/InAppMessaging][I-IAM230002] Loaded 0 clearcut log records from file in 0.000345 seconds
8.13.0 - [Firebase/InAppMessaging][I-IAM230005] Returning 0 clearcut retry records from popStillValidRecords
8.13.0 - [Firebase/InAppMessaging][I-IAM260001] FIRIAMClearcutUploader created with strategy as min wait time in seconds:300;max wait time in seconds:43200;failure backoff time in seconds:3600;batch send size:50
8.13.0 - [Firebase/InAppMessaging][I-IAM290001] SDK is in mode of Newly Installed and has seen 0 fetches.
8.13.0 - [Firebase/InAppMessaging][I-IAM300010] Detected 3 custom URL schemes from environment
8.13.0 - [Firebase/InAppMessaging][I-IAM180002] Firebase In-App Messaging SDK version 8.13.0 finished startup in 0.310259 seconds with these settings: APIServer:firebaseinappmessaging.googleapis.com;ProjectNumber:1007228000705; API_Key:AIzaSyBJxYMNc0aSToE8UA_RJTgTafMJylGg7-I;Clearcut Server:play.googleapis.com; Fetch Minimal Interval:86400 seconds; Activity Logger Max:100; Foreground Display Trigger Minimal Interval:86400 seconds;
8.13.0 - [Firebase/InAppMessaging][I-IAM150004] Persistent file path for fetch response data is /var/mobile/Containers/Data/Application/5BA94567-81A6-46ED-A1AC-696EFA9B729A/Library/Caches/firebase-iam-messages-cache
8.13.0 - [Firebase/InAppMessaging][I-IAM150003] Local fetch storage file not existent yet: first time launch of the app.
8.13.0 - [Firebase/InAppMessaging][I-IAM900014] No fetch epoch time detected in API response.
8.13.0 - [Firebase/InAppMessaging][I-IAM900002] 0 message definitions were parsed out successfully and 0 messages are discarded
8.13.0 - [Firebase/InAppMessaging][I-IAM160011] No analytics event trigger based messages, disable listening
8.13.0 - [Firebase/InAppMessaging][I-IAM140003] Stop observing Firebase Analytics events for display check.
8.13.0 - [Firebase/InAppMessaging][I-IAM160001] There are 0 test messages and 0 regular messages and 0 Firebase Analytics events to watch after resetting the message cache
8.13.0 - [Firebase/InAppMessaging][I-IAM180001] Message loading from fetch storage was done.
8.13.0 - [Firebase/InAppMessaging][I-IAM180014] No auto data collection enable setting entry detected.So no FIAM programmatic setting from the app.
8.13.0 - [Firebase/InAppMessaging][I-IAM180018] No programmatic or plist setting at FIAM level. Fallback to global Firebase level setting.
8.13.0 - [Firebase/InAppMessaging][I-IAM180009] No FIAM SDK startup due to settings.
8.13.0 - [Firebase/InAppMessaging][I-IAM310004] App will become inactive, save activity logs
8.13.0 - [Firebase/InAppMessaging][I-IAM310004] App will become inactive, save activity logs
8.13.0 - [Firebase/InAppMessaging][I-IAM230003] Saving 0 clearcut log records into file is successful
8.13.0 - [Firebase/InAppMessaging][I-IAM230003] Saving 0 clearcut log records into file is successful
8.13.0 - [Firebase/InAppMessaging][I-IAM260010] App foregrounded, FIRIAMClearcutUploader will seed next send
8.13.0 - [Firebase/InAppMessaging][I-IAM260006] Next upload attempt scheduled in 0 seconds
8.13.0 - [Firebase/InAppMessaging][I-IAM230005] Returning 0 clearcut retry records from popStillValidRecords
8.13.0 - [Firebase/InAppMessaging][I-IAM260007] No clearcut records to be uploaded
8.13.0 - [Firebase/InAppMessaging][I-IAM260010] App foregrounded, FIRIAMClearcutUploader will seed next send
8.13.0 - [Firebase/InAppMessaging][I-IAM260006] Next upload attempt scheduled in 0 seconds
8.13.0 - [Firebase/InAppMessaging][I-IAM230005] Returning 0 clearcut retry records from popStillValidRecords
8.13.0 - [Firebase/InAppMessaging][I-IAM260007] No clearcut records to be uploaded
8.13.0 - [Firebase/InAppMessaging][I-IAM310004] App will become inactive, save activity logs
8.13.0 - [Firebase/InAppMessaging][I-IAM310004] App will become inactive, save activity logs
8.13.0 - [Firebase/InAppMessaging][I-IAM230003] Saving 0 clearcut log records into file is successful
8.13.0 - [Firebase/InAppMessaging][I-IAM230003] Saving 0 clearcut log records into file is successful
8.13.0 - [Firebase/InAppMessaging][I-IAM310004] App will become inactive, save activity logs
8.13.0 - [Firebase/InAppMessaging][I-IAM310004] App will become inactive, save activity logs
8.13.0 - [Firebase/InAppMessaging][I-IAM230003] Saving 0 clearcut log records into file is successful
8.13.0 - [Firebase/InAppMessaging][I-IAM230003] Saving 0 clearcut log records into file is successful
8.13.0 - [Firebase/InAppMessaging][I-IAM310004] App will become inactive, save activity logs
8.13.0 - [Firebase/InAppMessaging][I-IAM310004] App will become inactive, save activity logs
8.13.0 - [Firebase/InAppMessaging][I-IAM230003] Saving 0 clearcut log records into file is successful
8.13.0 - [Firebase/InAppMessaging][I-IAM230003] Saving 0 clearcut log records into file is successful
sin2
commented
2 years ago FirebaseInAppMessagingAutomaticDataCollectionEnabled - setting this in my info.plist to TRUE worked for me
Step 0: Are you in the right place?
Yes
[REQUIRED] Step 1: Describe your environment
[REQUIRED] Step 2: Describe the problem
Steps to reproduce:
i would like to see Firebase Installation ID but not show in console simulation and real device have same problem before version i see it happen too i don't know what happen. I'm follow on this https://firebase.google.com/docs/in-app-messaging/get-started?authuser=1&platform=ios#get_your_apps_instance_id but not working to show Installation ID in log
Console Log: