Firebase does not map APNs token to FCM token in second installation of application

[REQUIRED] Step 1: Describe your environment

Xcode version: 11.6 And 12 (Tested with both)
Firebase SDK version: 6.30.0
Firebase Component: Messaging
Component version: 6.30.0
Installation method: CocoaPods

[REQUIRED] Step 2: Describe the problem
Steps to reproduce:
Hello everyone,
I faced an issue that when I install iOS application for the second time and so on, the firebase SDK does not map FCM token to APN token correctly.
For the first time everything works great and I can push to application via both FCM token and APN token. In the second installation I can not push to application via FCM token but APN token works correctly.
I tested to register my APN token with Google Server API and the token that I retrieve from server is different with the token that I retrieve from inside application. It is interesting to tell that token that I retrieve from server works.
I also tested method swizzling but it did not work.
Relevant Code:
Here is my Firebase Debug Full Log:
2020-10-19 11:04:20.592199+0330 dara[6317:2115277] 6.30.0 - [Firebase/Core][I-COR000001] Configuring the default app.
2020-10-19 11:04:20.598203+0330 dara[6317:2115277] 6.30.0 - [Firebase/Core][I-COR000033] Data Collection flag is not set.
2020-10-19 11:04:20.634967+0330 dara[6317:2115274] 6.30.0 - [Firebase/Analytics][I-ACS024001] Debug mode is off
2020-10-19 11:04:20.635053+0330 dara[6317:2115274] 6.30.0 - [Firebase/Analytics][I-ACS005000] The AdSupport Framework is not currently linked. Some features will not function properly. Learn more at http://goo.gl/9vSsPb
2020-10-19 11:04:20.636542+0330 dara[6317:2115275] 6.30.0 - [Firebase/Analytics][I-ACS023007] Analytics v.60702000 started
2020-10-19 11:04:20.636988+0330 dara[6317:2115275] 6.30.0 - [Firebase/Analytics][I-ACS023008] To enable debug logging set the following application argument: -FIRAnalyticsDebugEnabled (see http://goo.gl/RfcP7r)
2020-10-19 11:04:20.637399+0330 dara[6317:2115275] 6.30.0 - [Firebase/Analytics][I-ACS023009] Debug logging enabled
2020-10-19 11:04:20.637471+0330 dara[6317:2115275] 6.30.0 - [Firebase/Analytics][I-ACS023207] To enable verbose logging set the following application argument: -FIRAnalyticsVerboseLoggingEnabled (see http://goo.gl/RfcP7r)
2020-10-19 11:04:20.640612+0330 dara[6317:2115263] 6.30.0 - [Firebase/Installations][I-FIS002000] -[FIRInstallationsIDController createGetInstallationItemPromise], appName: __FIRAPP_DEFAULT
2020-10-19 11:04:20.642392+0330 dara[6317:2115274] 6.30.0 - [Firebase/InstanceID][I-IID023000] Info is not found in Keychain. OSStatus: -25300. Keychain query: {
2020-10-19 11:04:20.643026+0330 dara[6317:2115274] 6.30.0 - [Firebase/InstanceID][I-IID023000] Info is not found in Keychain. OSStatus: -25300. Keychain query: {
2020-10-19 11:04:20.643425+0330 dara[6317:2115274] 6.30.0 - [Firebase/InstanceID][I-IID007006] Checkin parameters: {
2020-10-19 11:04:20.644605+0330 dara[6317:2115275] 6.30.0 - [Firebase/InstanceID][I-IID005004] Checkin is in progress
11:04:20.645235+0330 dara[6317:2115275] 6.30.0 - [Firebase/Messaging][I-FCM002000] FIRMessaging library version 4.6.2
2020-10-19 11:04:20.652523+0330 dara[6317:2115275] 6.30.0 - [Firebase/Messaging][I-FCM001000] FIRMessaging Remote Notifications proxy enabled, will swizzle remote notification receiver handlers. If you'd prefer to manually integrate Firebase Messaging, add "FirebaseAppDelegateProxyEnabled" to your Info.plist, and set it to NO. Follow the instructions at:
https://firebase.google.com/docs/cloud-messaging/ios/client#method_swizzling_in_firebase_messaging
2020-10-19 11:04:20.873866+0330 dara[6317:2115269] 6.30.0 - [Firebase/Analytics][I-ACS002002] APMExperimentAlarm scheduled to fire in approx. (s): 9.999971985816956
2020-10-19 11:04:20.921000+0330 dara[6317:2115263] 6.30.0 - [Firebase/Analytics][I-ACS031025] Analytics screen reporting is enabled. Call +[FIRAnalytics logEventWithName:FIREventScreenView parameters:] to log a screen view event. To disable automatic screen reporting, set the flag FirebaseScreenReportingEnabled to NO (boolean) in the Info.plist
2020-10-19 11:04:21.100303+0330 dara[6317:2115263] 6.30.0 - [Firebase/Analytics][I-ACS031010] Tracking view controller. Class, ID: RNNSplashScreen, -7296444583548067707
2020-10-19 11:04:21.100407+0330 dara[6317:2115263] 6.30.0 - [Firebase/Analytics][I-ACS031013] Screen view event not logged. App is not active.
2020-10-19 11:04:21.101669+0330 dara[6317:2115269] 6.30.0 - [Firebase/Analytics][I-ACS800023] No pending snapshot to activate. SDK name: app_measurement
2020-10-19 11:04:21.101804+0330 dara[6317:2115269] 6.30.0 - [Firebase/Analytics][I-ACS031006] View controller already tracked. Class, ID: RNNSplashScreen, -7296444583548067707
2020-10-19 11:04:21.119410+0330 dara[6317:2115269] 6.30.0 - [Firebase/Installations][I-FIS002001] -[FIRInstallationsIDController installationWithValidAuthTokenForcingRefresh:0], appName: __FIRAPP_DEFAULT
2020-10-19 11:04:21.146103+0330 dara[6317:2115263] 6.30.0 - [Firebase/Installations][I-FIS001001] Sending request: <NSMutableURLRequest: 0x283340cc0> { URL: https://firebaseinstallations.googleapis.com/v1/projects/dara-71ef1/installations/ }, body:{"appId":"1:398151505418:ios:fe36dc08007c241fb171f3","fid":"fYZk9S-AeUtWnV54s5AfNt","authVersion":"FIS_v2","sdkVersion":"i:1.7.0"}, headers: {
    "X-firebase-client" = "apple-platform/ios apple-sdk/17G64 fire-analytics/6.7.2 fire-fcm/4.6.2 fire-iid/4.8.0 fire-install/1.7.0 fire-ios/6.10.0 react-native-firebase/8.4.5 swift/true xcode/11E708";
    "X-firebase-client-log-type" = 3;
2020-10-19 11:04:21.320026+0330 dara[6317:2115270] 6.30.0 - [Firebase/Analytics][I-ACS800023] No pending snapshot to activate. SDK name: app_measurement
2020-10-19 11:04:21.320261+0330 dara[6317:2115275] 6.30.0 - [Firebase/Analytics][I-ACS029017] Configuration was not found in database. The configuration will be fetched from the network when necessary
2020-10-19 11:04:21.320968+0330 dara[6317:2115270] 6.30.0 - [Firebase/Analytics][I-ACS023016] Analytics is ready to receive events
2020-10-19 11:04:21.330472+0330 dara[6317:2115275] 6.30.0 - [Firebase/Analytics][I-ACS023087] User property set. Name, value: _fi, 1
2020-10-19 11:04:21.332989+0330 dara[6317:2115275] 6.30.0 - [Firebase/Analytics][I-ACS023087] User property set. Name, value: _fot,<PHONE_NUMBER>000
2020-10-19 11:04:21.334505+0330 dara[6317:2115270] 6.30.0 - [Firebase/Analytics][I-ACS023051] Logging event: origin, name, params: auto, _f, {
2020-10-19 11:04:21.349561+0330 dara[6317:2115269] 6.30.0 - [Firebase/Analytics][I-ACS023072] Event logged. Event name, event params: _f, {
2020-10-19 11:04:21.352763+0330 dara[6317:2115275] 6.30.0 - [Firebase/Analytics][I-ACS002002] Measurement timer scheduled to fire in approx. (s): 13.85420000553131
2020-10-19 11:04:21.359941+0330 dara[6317:2115269] 6.30.0 - [Firebase/Analytics][I-ACS023087] User property set. Name, value: _sid,<PHONE_NUMBER>
2020-10-19 11:04:21.363672+0330 dara[6317:2115269] 6.30.0 - [Firebase/Analytics][I-ACS023087] User property set. Name, value: _sno, 1
2020-10-19 11:04:21.364287+0330 dara[6317:2115275] 6.30.0 - [Firebase/Analytics][I-ACS023051] Logging event: origin, name, params: auto, _s, {
2020-10-19 11:04:21.367738+0330 dara[6317:2115275] 6.30.0 - [Firebase/Analytics][I-ACS023072] Event logged. Event name, event params: _s, {
2020-10-19 11:04:21.369610+0330 dara[6317:2115275] 6.30.0 - [Firebase/Analytics][I-ACS002003] Measurement timer canceled
2020-10-19 11:04:21.369690+0330 dara[6317:2115275] 6.30.0 - [Firebase/Analytics][I-ACS002002] Measurement timer scheduled to fire in approx. (s): 13.83724594116211
2020-10-19 11:04:21.370136+0330 dara[6317:2115270] 6.30.0 - [Firebase/Analytics][I-ACS023051] Logging event: origin, name, params: auto, _e, {
2020-10-19 11:04:21.373705+0330 dara[6317:2115270] 6.30.0 - [Firebase/Analytics][I-ACS023072] Event logged. Event name, event params: _e, {
2020-10-19 11:04:21.375934+0330 dara[6317:2115275] 6.30.0 - [Firebase/Analytics][I-ACS002003] Measurement timer canceled
2020-10-19 11:04:21.376005+0330 dara[6317:2115275] 6.30.0 - [Firebase/Analytics][I-ACS002002] Measurement timer scheduled to fire in approx. (s): 13.83095598220825
2020-10-19 11:04:21.379679+0330 dara[6317:2115269] 6.30.0 - [Firebase/Analytics][I-ACS032003] iAd framework is not linked. Search Ad Attribution Reporter is disabled.
2020-10-19 11:04:21.380916+0330 dara[6317:2115269] 6.30.0 - [Firebase/Analytics][I-ACS002003] Measurement timer canceled
2020-10-19 11:04:21.380956+0330 dara[6317:2115269] 6.30.0 - [Firebase/Analytics][I-ACS002002] Measurement timer scheduled to fire in approx. (s): 13.82593894004822
2020-10-19 11:04:21.381142+0330 dara[6317:2115275] 6.30.0 - [Firebase/Analytics][I-ACS023012] Analytics collection enabled
2020-10-19 11:04:21.498400+0330 dara[6317:2115275] 6.30.0 - [Firebase/InstanceID][I-IID007002] Invalid last checkin timestamp 2020-10-19 07:34:21 +0000 in future.
2020-10-19 11:04:21.498501+0330 dara[6317:2115275] 6.30.0 - [Firebase/InstanceID][I-IID007003] Checkin successful with authId:<PHONE_NUMBER>310761615, digest: HH0uDwPmJf7UF1YIhfcq3g==, lastCheckinTimestamp:<PHONE_NUMBER>000
2020-10-19 11:04:21.498657+0330 dara[6317:2115275] 6.30.0 - [Firebase/InstanceID][I-IID005004] Successfully got checkin credentials
2020-10-19 11:04:21.504024+0330 dara[6317:2115270] 6.30.0 - [Firebase/InstanceID][I-IID008010] Checkin plist file is saved
2020-10-19 11:04:21.505270+0330 dara[6317:2115269] 6.30.0 - [Firebase/InstanceID][I-IID023002] Couldn't delete item from Keychain OSStatus: -25300 with the keychain query {
2020-10-19 11:04:21.508246+0330 dara[6317:2115270] 6.30.0 - [Firebase/Installations][I-FIS002000] -[FIRInstallationsIDController createGetInstallationItemPromise], appName: __FIRAPP_DEFAULT
2020-10-19 11:04:21.508308+0330 dara[6317:2115270] 6.30.0 - [Firebase/InstanceID][I-IID005002] Checkin success.
2020-10-19 11:04:21.508650+0330 dara[6317:2115270] 6.30.0 - [Firebase/InstanceID][I-IID014000] Fetch new token for authorizedEntity:<PHONE_NUMBER>18, scope: *
2020-10-19 11:04:21.830643+0330 dara[6317:2115270] 6.30.0 - [Firebase/Analytics][I-ACS031010] Tracking view controller. Class, ID: RNNSideMenuController, -7296444583548067706
2020-10-19 11:04:21.830708+0330 dara[6317:2115270] 6.30.0 - [Firebase/Analytics][I-ACS031013] Screen view event not logged. App is not active.
2020-10-19 11:04:21.830738+0330 dara[6317:2115270] 6.30.0 - [Firebase/Analytics][I-ACS031006] View controller already tracked. Class, ID: RNNSideMenuController, -7296444583548067706
2020-10-19 11:04:21.831440+0330 dara[6317:2115270] 6.30.0 - [Firebase/Analytics][I-ACS031010] Tracking view controller. Class, ID: RNNComponentViewController, -7296444583548067705
2020-10-19 11:04:21.831503+0330 dara[6317:2115270] 6.30.0 - [Firebase/Analytics][I-ACS031013] Screen view event not logged. App is not active.
2020-10-19 11:04:21.831580+0330 dara[6317:2115270] 6.30.0 - [Firebase/Analytics][I-ACS031006] View controller already tracked. Class, ID: RNNComponentViewController, -7296444583548067705
2020-10-19 11:04:21.928893+0330 dara[6317:2115270] 6.30.0 - [Firebase/Installations][I-FIS001003] Request response received: <NSMutableURLRequest: 0x283340cc0> { URL: https://firebaseinstallations.googleapis.com/v1/projects/dara-71ef1/installations/ }, error: (null), body: {
2020-10-19 11:04:21.970925+0330 dara[6317:2115263] 6.30.0 - [Firebase/Installations][I-FIS001005] Parsing server response for https://firebaseinstallations.googleapis.com/v1/projects/dara-71ef1/installations/.
2020-10-19 11:04:21.971460+0330 dara[6317:2115263] 6.30.0 - [Firebase/Installations][I-FIS001007] FIRInstallationsItem parsed successfully.
2020-10-19 11:04:22.018500+0330 dara[6317:2115269] 6.30.0 - [Firebase/InstanceID][I-IID020000] Register request to https://fcmtoken.googleapis.com/register content: X-osv=14.0.1&device=5755014659310761615&X-scope=*&plat=2&app=com.tosan.dara.tosan&app_ver=1.0.0&X-cliv=fiid-4.6.2&sender=398151505418&X-subtype=398151505418&appid=fYZk9S-AeUtWnV54s5AfNt&gmp_app_id=1:398151505418:ios:fe36dc08007c241fb171f3
2020-10-19 11:04:22.678558+0330 dara[6317:2115275] 6.30.0 - [Firebase/Analytics][I-ACS031010] Tracking view controller. Class, ID: RNNSideMenuController, -7296444583548067704
2020-10-19 11:04:22.678618+0330 dara[6317:2115275] 6.30.0 - [Firebase/Analytics][I-ACS031013] Screen view event not logged. App is not active.
2020-10-19 11:04:22.678692+0330 dara[6317:2115275] 6.30.0 - [Firebase/Analytics][I-ACS031006] View controller already tracked. Class, ID: RNNSideMenuController, -7296444583548067704
2020-10-19 11:04:22.679072+0330 dara[6317:2115270] 6.30.0 - [Firebase/Analytics][I-ACS031010] Tracking view controller. Class, ID: RNNComponentViewController, -7296444583548067703
2020-10-19 11:04:22.679655+0330 dara[6317:2115270] 6.30.0 - [Firebase/Analytics][I-ACS031013] Screen view event not logged. App is not active.
2020-10-19 11:04:22.679849+0330 dara[6317:2115270] 6.30.0 - [Firebase/Analytics][I-ACS031006] View controller already tracked. Class, ID: RNNComponentViewController, -7296444583548067703
2020-10-19 11:04:22.679973+0330 dara[6317:2115270] 6.30.0 - [Firebase/InstanceID][I-IID023002] Couldn't delete item from Keychain OSStatus: -25300 with the keychain query {
2020-10-19 11:04:22.684868+0330 dara[6317:2115263] 6.30.0 - [Firebase/InstanceID][I-IID014001] Token fetch successful, token: fYZk9S-AeUtWnV54s5AfNt:APA91bE4xJwtngJwRAfGWaGBInWbFY9ejOKaIMrPPBmvJZPAZHs77HNZTpyGak7JjhVGAty9Cve2C7ZTGs1QrerY1MDF1zgM6vMQ1KIQgjFZgQ0SXrKZrGxZZc2_0C_meewaGRYS5bRY, authorizedEntity:<PHONE_NUMBER>18, scope:*
2020-10-19 11:04:22.685377+0330 dara[6317:2115263] 6.30.0 - [Firebase/InstanceID][I-IID003010] Successfully fetched default token.
2020-10-19 11:04:22.685481+0330 dara[6317:2115263] 6.30.0 - [Firebase/InstanceID][I-IID003008] Got default token fYZk9S-AeUtWnV54s5AfNt:APA91bE4xJwtngJwRAfGWaGBInWbFY9ejOKaIMrPPBmvJZPAZHs77HNZTpyGak7JjhVGAty9Cve2C7ZTGs1QrerY1MDF1zgM6vMQ1KIQgjFZgQ0SXrKZrGxZZc2_0C_meewaGRYS5bRY
2020-10-19 11:04:22.897261+0330 dara[6317:2115277] 6.30.0 - [Firebase/Analytics][I-ACS031006] View controller already tracked. Class, ID: RNNComponentViewController, -7296444583548067703
2020-10-19 11:04:23.842429+0330 dara[6317:2115270] 6.30.0 - [Firebase/Analytics][I-ACS031010] Tracking view controller. Class, ID: RNNComponentViewController, -7296444583548067702
2020-10-19 11:04:23.842705+0330 dara[6317:2115270] 6.30.0 - [Firebase/Analytics][I-ACS031013] Screen view event not logged. App is not active.
2020-10-19 11:04:23.842768+0330 dara[6317:2115270] 6.30.0 - [Firebase/Analytics][I-ACS031006] View controller already tracked. Class, ID: RNNComponentViewController, -7296444583548067702
2020-10-19 11:04:24.753 [warn][tid:com.facebook.react.JavaScript] Usage of "messaging().registerDeviceForRemoteMessages()" is not required. You only need to register if auto-registration is disabled in your 'firebase.json' configuration file via the 'messaging_ios_auto_register_for_remote_messages' property.
2020-10-19 11:04:24.785354+0330 dara[6317:2115277] 6.30.0 - [Firebase/Installations][I-FIS002000] -[FIRInstallationsIDController createGetInstallationItemPromise], appName: __FIRAPP_DEFAULT
2020-10-19 11:04:24.785537+0330 dara[6317:2115277] 6.30.0 - [Firebase/Installations][I-FIS002001] -[FIRInstallationsIDController installationWithValidAuthTokenForcingRefresh:0], appName: __FIRAPP_DEFAULT
2020-10-19 11:04:24.797452+0330 dara[6317:2115279] 6.30.0 - [Firebase/Installations][I-FIS002000] -[FIRInstallationsIDController createGetInstallationItemPromise], appName: __FIRAPP_DEFAULT
2020-10-19 11:04:24.797756+0330 dara[6317:2115279] 6.30.0 - [Firebase/Installations][I-FIS002001] -[FIRInstallationsIDController installationWithValidAuthTokenForcingRefresh:0], appName: __FIRAPP_DEFAULT
2020-10-19 11:04:24.799193+0330 dara[6317:2115279] 6.30.0 - [Firebase/Installations][I-FIS002000] -[FIRInstallationsIDController createGetInstallationItemPromise], appName: __FIRAPP_DEFAULT
2020-10-19 11:04:24.800427+0330 dara[6317:2115270] 6.30.0 - [Firebase/Installations][I-FIS002001] -[FIRInstallationsIDController installationWithValidAuthTokenForcingRefresh:0], appName: __FIRAPP_DEFAULT
2020-10-19 11:04:24.801437+0330 dara[6317:2115275] 6.30.0 - [Firebase/Messaging][I-FCM017000] Topic subscription request: sender=fYZk9S-AeUtWnV54s5AfNt:APA91bE4xJwtngJwRAfGWaGBInWbFY9ejOKaIMrPPBmvJZPAZHs77HNZTpyGak7JjhVGAty9Cve2C7ZTGs1QrerY1MDF1zgM6vMQ1KIQgjFZgQ0SXrKZrGxZZc2_0C_meewaGRYS5bRY&app=com.tosan.dara.tosan&device=5755014659310761615&app_ver=1.0.0&X-gcm.topic=/topics/general&X-scope=/topics/general
2020-10-19 11:04:24.805769+0330 dara[6317:2115279] 6.30.0 - [Firebase/Messaging][I-FCM017000] Topic subscription request: sender=fYZk9S-AeUtWnV54s5AfNt:APA91bE4xJwtngJwRAfGWaGBInWbFY9ejOKaIMrPPBmvJZPAZHs77HNZTpyGak7JjhVGAty9Cve2C7ZTGs1QrerY1MDF1zgM6vMQ1KIQgjFZgQ0SXrKZrGxZZc2_0C_meewaGRYS5bRY&app=com.tosan.dara.tosan&device=5755014659310761615&app_ver=1.0.0&X-gcm.topic=/topics/mobileBank_general&X-scope=/topics/mobileBank_general
2020-10-19 11:04:25.599449+0330 dara[6317:2115269] 6.30.0 - [Firebase/Messaging][I-FCM004003] Successfully subscribed to topic /topics/general
2020-10-19 11:04:25.641282+0330 dara[6317:2115279] 6.30.0 - [Firebase/Messaging][I-FCM004003] Successfully subscribed to topic /topics/mobileBank_general
2020-10-19 11:04:26.073651+0330 dara[6317:2115269] 6.30.0 - [Firebase/InstanceID][I-IID003012] Provisioning profile has specifically provisioned devices, most likely a Dev profile.
2020-10-19 11:04:26.073779+0330 dara[6317:2115269] 6.30.0 - [Firebase/InstanceID][I-IID003013] APNS Environment in profile: development
2020-10-19 11:04:26.075794+0330 dara[6317:2115269] 6.30.0 - [Firebase/InstanceID][I-IID023000] Info is not found in Keychain. OSStatus: -25300. Keychain query: {
2020-10-19 11:04:26.206250+0330 dara[6317:2115270] 6.30.0 - [Firebase/Analytics][I-ACS002002] Engagement timer scheduled to fire in approx. (s): 3600
2020-10-19 11:04:26.208675+0330 dara[6317:2115270] 6.30.0 - [Firebase/Analytics][I-ACS023051] Logging event: origin, name, params: auto, _vs, {
2020-10-19 11:04:26.240651+0330 dara[6317:2115270] 6.30.0 - [Firebase/Analytics][I-ACS023072] Event logged. Event name, event params: _vs, {
2020-10-19 11:04:26.425655+0330 dara[6317:2115279] 6.30.0 - [Firebase/Analytics][I-ACS031006] View controller already tracked. Class, ID: RNNComponentViewController, -7296444583548067702
2020-10-19 11:04:30.874743+0330 dara[6317:2115270] 6.30.0 - [Firebase/Analytics][I-ACS002001] APMExperimentAlarm fired
2020-10-19 11:04:30.874847+0330 dara[6317:2115270] 6.30.0 - [Firebase/Analytics][I-ACS002003] APMExperimentAlarm canceled
2020-10-19 11:04:31.468048+0330 dara[6317:2115277] 6.30.0 - [Firebase/Analytics][I-ACS002002] APMExperimentAlarm scheduled to fire in approx. (s): 14399.97864305973
2020-10-19 11:04:35.286034+0330 dara[6317:2115274] 6.30.0 - [Firebase/Analytics][I-ACS002001] Measurement timer fired
2020-10-19 11:04:35.286190+0330 dara[6317:2115274] 6.30.0 - [Firebase/Analytics][I-ACS002003] Measurement timer canceled
2020-10-19 11:04:35.296444+0330 dara[6317:2115277] 6.30.0 - [Firebase/Analytics][I-ACS900001] Downloading data. Host: https://app-measurement.com/config/app/1:398151505418:ios:fe36dc08007c241fb171f3?platform=ios&app_instance_id=21BADBCC085044A6B67F741FC5BEFE64&gmp_version=60702
2020-10-19 11:04:35.842405+0330 dara[6317:2115263] 6.30.0 - [Firebase/Analytics][I-ACS901006] Received SSL challenge for host. Host: https://app-measurement.com/config/app/1:398151505418:ios:fe36dc08007c241fb171f3?platform=ios&app_instance_id=21BADBCC085044A6B67F741FC5BEFE64&gmp_version=60702
2020-10-19 11:04:36.092363+0330 dara[6317:2115269] 6.30.0 - [Firebase/Analytics][I-ACS029014] Successfully parsed a configuration. Version:<PHONE_NUMBER>496339
2020-10-19 11:04:36.100383+0330 dara[6317:2115269] 6.30.0 - [Firebase/Analytics][I-ACS023105] Event is not subject to real-time event count daily limit. Marking an event as real-time. Event name, parameters: _f, {
2020-10-19 11:04:36.104957+0330 dara[6317:2115263] 6.30.0 - [Firebase/Analytics][I-ACS012018] Saving bundle. size (bytes): 328
2020-10-19 11:04:36.105140+0330 dara[6317:2115263] 6.30.0 - [Firebase/Analytics][I-ACS023116] Bundle added to the upload queue. BundleID, timestamp (ms): 1,<PHONE_NUMBER>206
2020-10-19 11:04:36.111924+0330 dara[6317:2115269] 6.30.0 - [Firebase/Analytics][I-ACS023087] User property set. Name, value: _lte, 1
2020-10-19 11:04:36.112455+0330 dara[6317:2115269] 6.30.0 - [Firebase/Analytics][I-ACS023087] User property set. Name, value: _se, 1
2020-10-19 11:04:36.115610+0330 dara[6317:2115269] 6.30.0 - [Firebase/Analytics][I-ACS012018] Saving bundle. size (bytes): 446
2020-10-19 11:04:36.115872+0330 dara[6317:2115269] 6.30.0 - [Firebase/Analytics][I-ACS023116] Bundle added to the upload queue. BundleID, timestamp (ms): 2,<PHONE_NUMBER>207
2020-10-19 11:04:36.120213+0330 dara[6317:2115269] 6.30.0 - [Firebase/Analytics][I-ACS023039] Measurement data sent to network. Timestamp (ms), data:<PHONE_NUMBER>119, <APMPBMeasurementBatch: 0x2833499b0>
2020-10-19 11:04:36.124385+0330 dara[6317:2115263] 6.30.0 - [Firebase/Analytics][I-ACS900000] Uploading data. Host: https://app-measurement.com/a
2020-10-19 11:04:36.428066+0330 dara[6317:2115274] 6.30.0 - [Firebase/Analytics][I-ACS901006] Received SSL challenge for host. Host: https://app-measurement.com/a
2020-10-19 11:04:36.662961+0330 dara[6317:2115270] 6.30.0 - [Firebase/Analytics][I-ACS023044] Successful upload. Got network response. Code, size: 204, -1
2020-10-19 11:04:36.668885+0330 dara[6317:2115263] 6.30.0 - [Firebase/Analytics][I-ACS002002] Measurement timer scheduled to fire in approx. (s): 9.992522835731506
2020-10-19 11:04:36.681139+0330 dara[6317:2115274] 6.30.0 - [Firebase/Analytics][I-ACS002003] Measurement timer canceled
2020-10-19 11:06:19.121790+0330 dara[6317:2116276] 6.30.0 - [Firebase/Analytics][I-ACS002003] Engagement timer canceled
2020-10-19 11:06:19.121877+0330 dara[6317:2116276] 6.30.0 - [Firebase/Analytics][I-ACS002002] Engagement timer scheduled to fire in approx. (s): 3600
2020-10-19 11:06:19.122650+0330 dara[6317:2116276] 6.30.0 - [Firebase/Analytics][I-ACS002003] Engagement timer canceled
2020-10-19 11:06:19.215157+0330 dara[6317:2116314] 6.30.0 - [Firebase/Analytics][I-ACS023051] Logging event: origin, name, params: auto, _e, {
2020-10-19 11:06:19.267235+0330 dara[6317:2116314] 6.30.0 - [Firebase/Analytics][I-ACS023072] Event logged. Event name, event params: _e, {
2020-10-19 11:06:19.270153+0330 dara[6317:2116314] 6.30.0 - [Firebase/Analytics][I-ACS002002] Measurement timer scheduled to fire in approx. (s): 3497.391204833984
2020-10-19 11:06:19.270596+0330 dara[6317:2116314] 6.30.0 - [Firebase/Analytics][I-ACS023051] Logging event: origin, name, params: auto, _ab, {
2020-10-19 11:06:19.274124+0330 dara[6317:2116314] 6.30.0 - [Firebase/Analytics][I-ACS023072] Event logged. Event name, event params: _ab, {
2020-10-19 11:06:19.276474+0330 dara[6317:2116314] 6.30.0 - [Firebase/Analytics][I-ACS002003] Measurement timer canceled
2020-10-19 11:06:19.276534+0330 dara[6317:2116314] 6.30.0 - [Firebase/Analytics][I-ACS002002] Measurement timer scheduled to fire in approx. (s): 3497.384779930115
2020-10-19 11:06:19.283668+0330 dara[6317:2116085] 6.30.0 - [Firebase/Analytics][I-ACS023087] User property set. Name, value: _lte, 112914
2020-10-19 11:06:19.284089+0330 dara[6317:2116085] 6.30.0 - [Firebase/Analytics][I-ACS023087] User property set. Name, value: _se, 112914
2020-10-19 11:06:19.286910+0330 dara[6317:2116085] 6.30.0 - [Firebase/Analytics][I-ACS012018] Saving bundle. size (bytes): 442
2020-10-19 11:06:19.287050+0330 dara[6317:2116085] 6.30.0 - [Firebase/Analytics][I-ACS023116] Bundle added to the upload queue. BundleID, timestamp (ms): 3,<PHONE_NUMBER>120
2020-10-19 11:06:19.289597+0330 dara[6317:2116085] 6.30.0 - [Firebase/Analytics][I-ACS023039] Measurement data sent to network. Timestamp (ms), data:<PHONE_NUMBER>289, <APMPBMeasurementBatch: 0x283341f80>
2020-10-19 11:06:19.292298+0330 dara[6317:2116085] 6.30.0 - [Firebase/Analytics][I-ACS900000] Uploading data. Host: https://app-measurement.com/a
2020-10-19 11:06:19.639707+0330 dara[6317:2116312] 6.30.0 - [Firebase/Analytics][I-ACS901006] Received SSL challenge for host. Host: https://app-measurement.com/a
2020-10-19 11:06:20.090474+0330 dara[6317:2116314] 6.30.0 - [Firebase/Analytics][I-ACS023044] Successful upload. Got network response. Code, size: 204, -1
2020-10-19 11:06:20.100189+0330 dara[6317:2116314] 6.30.0 - [Firebase/Analytics][I-ACS002003] Measurement timer canceled
2020-10-19 11:06:20.100344+0330 dara[6317:2116314] 6.30.0 - [Firebase/Analytics][I-ACS023142] Cancelling background upload task. Task ID : 14
2020-10-19 11:06:26.171679+0330 dara[6317:2116276] [connection] nw_resolver_start_query_timer_block_invoke [C21] Query fired: did not receive all answers in time for firebaseinstallations.googleapis.com:443
2020-10-19 11:06:26.464102+0330 dara[6317:2116085] 6.30.0 - [Firebase/Analytics][I-ACS002002] Engagement timer scheduled to fire in approx. (s): 3600
2020-10-19 11:07:16.769785+0330 dara[6317:2116713] 6.30.0 - [Firebase/Messaging][I-FCM018001] Device has capacity 61015 MB with 15770 MB free.
2020-10-19 11:07:16.770558+0330 dara[6317:2116713] 6.30.0 - [Firebase/Messaging][I-FCM006000] Received message missing local start time, dropped.
2020-10-19 11:07:16.770639+0330 dara[6317:2116713] 6.30.0 - [Firebase/Messaging][I-FCM019005] FIRMessagingAnalytics: Sending event: _nf params: {
2020-10-19 11:07:16.771231+0330 dara[6317:2116713] 6.30.0 - [Firebase/Messaging][I-FCM006000] Received message missing local start time, dropped.
2020-10-19 11:07:16.772917+0330 dara[6317:2116563] 6.30.0 - [Firebase/Messaging][I-FCM016004] Added sync message to cache:<PHONE_NUMBER>592529
2020-10-19 11:07:16.826660+0330 dara[6317:2116738] 6.30.0 - [Firebase/Analytics][I-ACS023051] Logging event: origin, name, params: fcm, _nf, {
2020-10-19 11:07:16.892010+0330 dara[6317:2116737] 6.30.0 - [Firebase/Analytics][I-ACS023072] Event logged. Event name, event params: _nf, {
2020-10-19 11:07:16.895682+0330 dara[6317:2116737] 6.30.0 - [Firebase/Analytics][I-ACS002002] Measurement timer scheduled to fire in approx. (s): 3543.194695949554
2020-10-19 11:07:17.297459+0330 dara[6317:2116737] 6.30.0 - [Firebase/Analytics][I-ACS031010] Tracking view controller. Class, ID: UIAlertController, -7296444583548067701
2020-10-19 11:07:17.298896+0330 dara[6317:2116737] 6.30.0 - [Firebase/Analytics][I-ACS002003] Engagement timer canceled
2020-10-19 11:07:17.298947+0330 dara[6317:2116737] 6.30.0 - [Firebase/Analytics][I-ACS002002] Engagement timer scheduled to fire in approx. (s): 3600
2020-10-19 11:07:17.300045+0330 dara[6317:2116737] 6.30.0 - [Firebase/Analytics][I-ACS023051] Logging event: origin, name, params: auto, _e, {
2020-10-19 11:07:17.307973+0330 dara[6317:2116737] 6.30.0 - [Firebase/Analytics][I-ACS023072] Event logged. Event name, event params: _e, {
2020-10-19 11:07:17.311061+0330 dara[6317:2116738] 6.30.0 - [Firebase/Analytics][I-ACS002003] Measurement timer canceled
2020-10-19 11:07:17.311136+0330 dara[6317:2116738] 6.30.0 - [Firebase/Analytics][I-ACS002002] Measurement timer scheduled to fire in approx. (s): 3542.779326915741
2020-10-19 11:07:17.311878+0330 dara[6317:2116713] 6.30.0 - [Firebase/Analytics][I-ACS023051] Logging event: origin, name, params: auto, _vs, {
2020-10-19 11:07:17.316223+0330 dara[6317:2116713] 6.30.0 - [Firebase/Analytics][I-ACS023072] Event logged. Event name, event params: _vs, {
2020-10-19 11:07:17.319355+0330 dara[6317:2116713] 6.30.0 - [Firebase/Analytics][I-ACS002003] Measurement timer canceled
2020-10-19 11:07:17.319681+0330 dara[6317:2116737] 6.30.0 - [Firebase/Analytics][I-ACS002002] Measurement timer scheduled to fire in approx. (s): 3542.771024942398
2020-10-19 11:07:19.413238+0330 dara[6317:2116715] 6.30.0 - [Firebase/Analytics][I-ACS031010] Tracking view controller. Class, ID: RNNComponentViewController, -7296444583548067702
2020-10-19 11:07:19.415250+0330 dara[6317:2116713] 6.30.0 - [Firebase/Analytics][I-ACS002003] Engagement timer canceled
2020-10-19 11:07:19.415651+0330 dara[6317:2116713] 6.30.0 - [Firebase/Analytics][I-ACS002002] Engagement timer scheduled to fire in approx. (s): 3600
2020-10-19 11:07:19.416533+0330 dara[6317:2116737] 6.30.0 - [Firebase/Analytics][I-ACS023051] Logging event: origin, name, params: auto, _e, {
2020-10-19 11:07:19.423610+0330 dara[6317:2116563] 6.30.0 - [Firebase/Analytics][I-ACS023072] Event logged. Event name, event params: _e, {
2020-10-19 11:07:19.426819+0330 dara[6317:2116737] 6.30.0 - [Firebase/Analytics][I-ACS002003] Measurement timer canceled
2020-10-19 11:07:19.426879+0330 dara[6317:2116737] 6.30.0 - [Firebase/Analytics][I-ACS002002] Measurement timer scheduled to fire in approx. (s): 3540.663610935211
2020-10-19 11:07:19.427787+0330 dara[6317:2116713] 6.30.0 - [Firebase/Analytics][I-ACS023051] Logging event: origin, name, params: auto, _vs, {
2020-10-19 11:07:19.431109+0330 dara[6317:2116563] 6.30.0 - [Firebase/Analytics][I-ACS023072] Event logged. Event name, event params: _vs, {
2020-10-19 11:07:19.432858+0330 dara[6317:2116713] 6.30.0 - [Firebase/Analytics][I-ACS002003] Measurement timer canceled
2020-10-19 11:07:19.432896+0330 dara[6317:2116713] 6.30.0 - [Firebase/Analytics][I-ACS002002] Measurement timer scheduled to fire in approx. (s): 3540.657490849495

Here is My FCM Token Log :
2020-10-19 11:04:22.684997+0330 dara[6317:2115062] FCM registration token: fYZk9S-AeUtWnV54s5AfNt:APA91bE4xJwtngJwRAfGWaGBInWbFY9ejOKaIMrPPBmvJZPAZHs77HNZTpyGak7JjhVGAty9Cve2C7ZTGs1QrerY1MDF1zgM6vMQ1KIQgjFZgQ0SXrKZrGxZZc2_0C_meewaGRYS5bRY

My APN Token Log:
2020-10-19 11:04:26.059656+0330 dara[6317:2115062] APN token:e3f9c5ed4674ae556f6be8c844ff2127d8d7b91a91f012fa6038a9b5518febfc

My Request and Response to Google server API:
Request :
{
    "application": "com.tosan.dara.tosan",
    "sandbox": true,
    "apns_tokens": [
        "e3f9c5ed4674ae556f6be8c844ff2127d8d7b91a91f012fa6038a9b5518febfc"
    ]
}

Response :
{
    "results": [
        {
            "registration_token": "fPGfx4fy920:APA91bGHHs3MA9FA7GzW0Z8vKkRx7RqpcTSEtjqHXq2BZZ3wEFnP52o4ErnxJrzYbiiNPpNyjTmaBcyZQ1yicHBh6oBoSDnTs0jVYQGhhATJtd_xNnsAQgDNx8P4Bv2S6AzVyQ0EkjE7",
            "apns_token": "e3f9c5ed4674ae556f6be8c844ff2127d8d7b91a91f012fa6038a9b5518febfc",
            "status": "OK"
        }
    ]
}

As you can see the FCM token from google server and application is different.

I've find out that if I open the application for second time or third time firebase successfully register APN token and refresh my FCM token.
But I need to register APN token at the first time.

Can you check if the patch in #6553 fixes this issue as well?

Can you check if the patch in #6553 fixes this issue as well?

Are there any cases that  cachedTokenIfAvailable return a token but cachedTokenInfos return nil ? Therefor if ([self.tokenManager checkTokenRefreshPolicyWithIID:identifier]) can't clean up expired tokens.
I'm facing a problem that at the first fresh install, i got a old token and push will not work. But the second fresh install or just second run -> new token fetched -> push work normal.

Can you check if the patch in #6553 fixes this issue as well?

Thanks for your response, unfortunately I've applied the patch (Just change my FIRInstanceID.m file) and it did not work. There is a delay in my code between calling [FIRApp configure] and calling registerForRemoteNotifications.
After I calling registerForRemoteNotifications the APN token fetched successfully and didRegisterForRemoteNotificationsWithDeviceToken method called. But firebase did not renew token and map to new APN token.

After a lots of debugging in firebase iOS SDK , I figured it out that inside class FIRInstanceIDTokenManager.m inside method updateTokensToAPNSDeviceToken the *tokenInfos variable's length is 0. It seems that if there is a delay between fetching APN token and FCM token , after the APN token has been fetched this variable should has 1 old FCM token. I do not know that this causes the problem but I will keep debugging.

It seems that if I force firebase to refresh token something like below code it will work, but i think it is not a permanent solution.
Here is my part of AppDelegate.m class:
- (void)application:(UIApplication *)app
        didRegisterForRemoteNotificationsWithDeviceToken:(NSData *)devToken {

  //[FIRMessaging messaging].APNSToken = devToken;

  [[FIRInstanceID instanceID] tokenWithAuthorizedEntity:@"********" scope:kFIRInstanceIDScopeFirebaseMessaging options:@{@"apns_token": devToken} handler:^(NSString * _Nullable token, NSError * _Nullable error) {
      NSLog(@"Error in refetching token:%@", error);
    // Fetch the token or error
}];

  NSUInteger dataLength = devToken.length;
  if (dataLength == 0) {
    return;
  }
  const unsigned char *dataBuffer = (const unsigned char *)devToken.bytes;
  NSMutableString *hexString  = [NSMutableString stringWithCapacity:(dataLength * 2)];
  for (int i = 0; i < dataLength; ++i) {
    [hexString appendFormat:@"%02x", dataBuffer[i]];
  }
  NSLog(@"APN token:%@", hexString);
}

But I will keep testing.

Thanks for the detailed investigation @shayantabatabaee. @chliangGoogle can you take a look?

@shayantabatabaee Can you patch the change in https://github.com/firebase/firebase-ios-sdk/pull/6669 and send us the debuglog?
To enable debug logging set the following application argument: -FIRDebugEnabled (see http://goo.gl/RfcP7r)

@morganchen12 and @chliangGoogle thanks for your time, yes I tested with the patch and full debug log is :
2020-10-20 23:29:50.771090+0330 dara[1314:192670] 6.34.0 - [Firebase/Core][I-COR000001] Configuring the default app.
2020-10-20 23:29:50.862980+0330 dara[1314:192677] 6.34.0 - [Firebase/Core][I-COR000033] Data Collection flag is not set.
2020-10-20 23:29:50.863073+0330 dara[1314:192677] 6.34.0 - [Firebase/Installations][I-FIS002000] -[FIRInstallationsIDController createGetInstallationItemPromise], appName: __FIRAPP_DEFAULT
2020-10-20 23:29:50.863103+0330 dara[1314:192677] 6.34.0 - [Firebase/Analytics][I-ACS024001] Debug mode is off
2020-10-20 23:29:50.863133+0330 dara[1314:192677] 6.34.0 - [Firebase/Analytics][I-ACS005000] The AdSupport Framework is not currently linked. Some features will not function properly. Learn more at http://goo.gl/9vSsPb
2020-10-20 23:29:50.863163+0330 dara[1314:192677] 6.34.0 - [Firebase/Analytics][I-ACS023007] Analytics v.60900000 started
2020-10-20 23:29:50.864257+0330 dara[1314:192677] 6.34.0 - [Firebase/Analytics][I-ACS023008] To enable debug logging set the following application argument: -FIRAnalyticsDebugEnabled (see http://goo.gl/RfcP7r)
2020-10-20 23:29:50.864933+0330 dara[1314:192677] 6.34.0 - [Firebase/Analytics][I-ACS023009] Debug logging enabled
2020-10-20 23:29:50.865116+0330 dara[1314:192677] 6.34.0 - [Firebase/Analytics][I-ACS023207] To enable verbose logging set the following application argument: -FIRAnalyticsVerboseLoggingEnabled (see http://goo.gl/RfcP7r)
2020-10-20 23:29:50.865166+0330 dara[1314:192677] 6.34.0 - [Firebase/InstanceID][I-IID008009] Deleted checkin plist file.
3:29:50.865268+0330 dara[1314:192677] 6.34.0 - [Firebase/InstanceID][I-IID007006] Checkin parameters: {
2020-10-20 23:29:50.865498+0330 dara[1314:192677] 6.34.0 - [Firebase/Messaging][I-FCM002000] FIRMessaging library version 4.7.1
0-10-20 23:29:50.865706+0330 dara[1314:192677] 6.34.0 - [Firebase/Messaging][I-FCM001000] FIRMessaging Remote Notifications proxy enabled, will swizzle remote notification receiver handlers. If you'd prefer to manually integrate Firebase Messaging, add "FirebaseAppDelegateProxyEnabled" to your Info.plist, and set it to NO. Follow the instructions at:
https://firebase.google.com/docs/cloud-messaging/ios/client#method_swizzling_in_firebase_messaging
2020-10-20 23:29:51.183817+0330 dara[1314:192677] 6.34.0 - [Firebase/InstanceID][I-IID013002] Removed cached checkin preferences from Keychain because this is a fresh install.
2020-10-20 23:29:51.184043+0330 dara[1314:192677] 6.34.0 - [Firebase/InstanceID][I-IID013006] App reset detected. Will delete server registrations.
2020-10-20 23:29:51.184306+0330 dara[1314:192677] 6.34.0 - [Firebase/Installations][I-FIS002001] -[FIRInstallationsIDController installationWithValidAuthTokenForcingRefresh:0], appName: __FIRAPP_DEFAULT
2020-10-20 23:29:51.248460+0330 dara[1314:192675] 6.34.0 - [Firebase/Analytics][I-ACS002002] APMExperimentAlarm scheduled to fire in approx. (s): 9.999974966049194
2020-10-20 23:29:51.284452+0330 dara[1314:192670] 6.34.0 - [Firebase/Analytics][I-ACS031010] Tracking view controller. Class, ID: RNNSplashScreen, -3628088477171312220
2020-10-20 23:29:51.284534+0330 dara[1314:192670] 6.34.0 - [Firebase/Analytics][I-ACS031013] Screen view event not logged. App is not active.
2020-10-20 23:29:51.284615+0330 dara[1314:192670] 6.34.0 - [Firebase/Analytics][I-ACS031006] View controller already tracked. Class, ID: RNNSplashScreen, -3628088477171312220
2020-10-20 23:29:51.312529+0330 dara[1314:192673] 6.34.0 - [Firebase/InstanceID][I-IID014012] Invalidating cached token for<PHONE_NUMBER>18 (*) due to token is no longer fresh.
2020-10-20 23:29:51.312655+0330 dara[1314:192673] 6.34.0 - [Firebase/InstanceID][I-IID005004] Checkin is in progress
2020-10-20 23:29:51.334640+0330 dara[1314:192677] 6.34.0 - [Firebase/Installations][I-FIS001001] Sending request: <NSMutableURLRequest: 0x2834fc670> { URL: https://firebaseinstallations.googleapis.com/v1/projects/dara-71ef1/installations/ }, body:{"appId":"1:398151505418:ios:fe36dc08007c241fb171f3","fid":"dbAoN1EVVUmpj3Vgj8-70_","authVersion":"FIS_v2","sdkVersion":"i:1.7.0"}, headers: {
    "X-firebase-client" = "apple-platform/ios apple-sdk/17G64 fire-analytics/6.9.0 fire-fcm/4.7.1 fire-iid/4.8.0 fire-install/1.7.0 fire-ios/6.10.4 react-native-firebase/8.4.6 swift/true xcode/11E708";
    "X-firebase-client-log-type" = 3;
2020-10-20 23:29:51.463358+0330 dara[1314:192677] 6.34.0 - [Firebase/Analytics][I-ACS800023] No pending snapshot to activate. SDK name: app_measurement
2020-10-20 23:29:51.463680+0330 dara[1314:192677] 6.34.0 - [Firebase/Analytics][I-ACS029017] Configuration was not found in database. The configuration will be fetched from the network when necessary
2020-10-20 23:29:51.463808+0330 dara[1314:192677] 6.34.0 - [Firebase/Analytics][I-ACS023016] Analytics is ready to receive events
2020-10-20 23:29:51.479175+0330 dara[1314:192670] 6.34.0 - [Firebase/Analytics][I-ACS023087] User property set. Name, value: _fi, 1
2020-10-20 23:29:51.510639+0330 dara[1314:192670] 6.34.0 - [Firebase/Analytics][I-ACS023087] User property set. Name, value: _fot,<PHONE_NUMBER>000
2020-10-20 23:29:51.512955+0330 dara[1314:192673] 6.34.0 - [Firebase/Analytics][I-ACS023051] Logging event: origin, name, params: auto, _f, {
2020-10-20 23:29:51.540934+0330 dara[1314:192673] 6.34.0 - [Firebase/Analytics][I-ACS023072] Event logged. Event name, event params: _f, {
2020-10-20 23:29:51.543569+0330 dara[1314:192673] 6.34.0 - [Firebase/Analytics][I-ACS002002] Measurement timer scheduled to fire in approx. (s): 14.01439714431763
2020-10-20 23:29:51.556849+0330 dara[1314:192677] 6.34.0 - [Firebase/Analytics][I-ACS023087] User property set. Name, value: _sid,<PHONE_NUMBER>
2020-10-20 23:29:51.563886+0330 dara[1314:192670] 6.34.0 - [Firebase/Analytics][I-ACS023087] User property set. Name, value: _sno, 1
2020-10-20 23:29:51.564441+0330 dara[1314:192677] 6.34.0 - [Firebase/Analytics][I-ACS023051] Logging event: origin, name, params: auto, _s, {
2020-10-20 23:29:51.568582+0330 dara[1314:192670] 6.34.0 - [Firebase/Analytics][I-ACS023072] Event logged. Event name, event params: _s, {
2020-10-20 23:29:51.571936+0330 dara[1314:192670] 6.34.0 - [Firebase/Analytics][I-ACS002003] Measurement timer canceled
2020-10-20 23:29:51.572128+0330 dara[1314:192670] 6.34.0 - [Firebase/Analytics][I-ACS002002] Measurement timer scheduled to fire in approx. (s): 13.98711514472961
2020-10-20 23:29:51.573374+0330 dara[1314:192677] 6.34.0 - [Firebase/Analytics][I-ACS023051] Logging event: origin, name, params: auto, _e, {
2020-10-20 23:29:51.577326+0330 dara[1314:192670] 6.34.0 - [Firebase/Analytics][I-ACS023072] Event logged. Event name, event params: _e, {
2020-10-20 23:29:51.587036+0330 dara[1314:192677] 6.34.0 - [Firebase/Analytics][I-ACS002003] Measurement timer canceled
2020-10-20 23:29:51.587138+0330 dara[1314:192677] 6.34.0 - [Firebase/Analytics][I-ACS002002] Measurement timer scheduled to fire in approx. (s): 13.97123718261719
2020-10-20 23:29:51.598771+0330 dara[1314:192670] 6.34.0 - [Firebase/Analytics][I-ACS032003] iAd framework is not linked. Search Ad Attribution Reporter is disabled.
2020-10-20 23:29:51.601963+0330 dara[1314:192677] 6.34.0 - [Firebase/Analytics][I-ACS002003] Measurement timer canceled
2020-10-20 23:29:51.602077+0330 dara[1314:192677] 6.34.0 - [Firebase/Analytics][I-ACS002002] Measurement timer scheduled to fire in approx. (s): 13.95647811889648
2020-10-20 23:29:51.602120+0330 dara[1314:192677] 6.34.0 - [Firebase/Analytics][I-ACS023012] Analytics collection enabled
2020-10-20 23:29:51.602345+0330 dara[1314:192677] 6.34.0 - [Firebase/Analytics][I-ACS023220] Analytics screen reporting is enabled. Call +[FIRAnalytics logEventWithName:FIREventScreenView parameters:] to log a screen view event. To disable automatic screen reporting, set the flag FirebaseAutomaticScreenReportingEnabled to NO (boolean) in the Info.plist
0 23:29:51.798300+0330 dara[1314:192677] 6.34.0 - [Firebase/InstanceID][I-IID007002] Invalid last checkin timestamp 2020-10-20 19:59:51 +0000 in future.
2020-10-20 23:29:51.798422+0330 dara[1314:192677] 6.34.0 - [Firebase/InstanceID][I-IID007003] Checkin successful with authId:<PHONE_NUMBER>867869039, digest: xQ+yPjgEysYQwLSoJuTp/A==, lastCheckinTimestamp:<PHONE_NUMBER>000
2020-10-20 23:29:51.798598+0330 dara[1314:192677] 6.34.0 - [Firebase/InstanceID][I-IID005004] Successfully got checkin credentials
2020-10-20 23:29:51.800784+0330 dara[1314:192670] 6.34.0 - [Firebase/InstanceID][I-IID008010] Checkin plist file is saved
2020-10-20 23:29:51.800945+0330 dara[1314:192670] 6.34.0 - [Firebase/InstanceID][I-IID023002] Couldn't delete item from Keychain OSStatus: -25300 with the keychain query {
2020-10-20 23:29:51.802493+0330 dara[1314:192670] 6.34.0 - [Firebase/InstanceID][I-IID005002] Checkin success.
2020-10-20 23:29:51.802542+0330 dara[1314:192670] 6.34.0 - [Firebase/Installations][I-FIS002000] -[FIRInstallationsIDController createGetInstallationItemPromise], appName: __FIRAPP_DEFAULT
2020-10-20 23:29:51.803003+0330 dara[1314:192675] 6.34.0 - [Firebase/InstanceID][I-IID014000] Fetch new token for authorizedEntity:<PHONE_NUMBER>18, scope: *
2020-10-20 23:29:52.052564+0330 dara[1314:192670] 6.34.0 - [Firebase/Analytics][I-ACS031010] Tracking view controller. Class, ID: RNNSideMenuController, -3628088477171312219
2020-10-20 23:29:52.053075+0330 dara[1314:192670] 6.34.0 - [Firebase/Analytics][I-ACS031013] Screen view event not logged. App is not active.
2020-10-20 23:29:52.053446+0330 dara[1314:192670] 6.34.0 - [Firebase/Analytics][I-ACS031006] View controller already tracked. Class, ID: RNNSideMenuController, -3628088477171312219
2020-10-20 23:29:52.053732+0330 dara[1314:192670] 6.34.0 - [Firebase/Analytics][I-ACS031010] Tracking view controller. Class, ID: RNNComponentViewController, -3628088477171312218
2020-10-20 23:29:52.053933+0330 dara[1314:192670] 6.34.0 - [Firebase/Analytics][I-ACS031013] Screen view event not logged. App is not active.
2020-10-20 23:29:52.054192+0330 dara[1314:192670] 6.34.0 - [Firebase/Analytics][I-ACS031006] View controller already tracked. Class, ID: RNNComponentViewController, -3628088477171312218
2020-10-20 23:29:52.546607+0330 dara[1314:192673] 6.34.0 - [Firebase/Installations][I-FIS001003] Request response received: <NSMutableURLRequest: 0x2834fc670> { URL: https://firebaseinstallations.googleapis.com/v1/projects/dara-71ef1/installations/ }, error: (null), body: {
2020-10-20 23:29:52.546839+0330 dara[1314:192670] 6.34.0 - [Firebase/Installations][I-FIS001005] Parsing server response for https://firebaseinstallations.googleapis.com/v1/projects/dara-71ef1/installations/.
2020-10-20 23:29:52.546893+0330 dara[1314:192670] 6.34.0 - [Firebase/Installations][I-FIS001007] FIRInstallationsItem parsed successfully.
2020-10-20 23:29:52.555487+0330 dara[1314:192670] 6.34.0 - [Firebase/InstanceID][I-IID021000] Unregister request to https://fcmtoken.googleapis.com/register content: X-osv=14.0.1&device=4776107188660600225&plat=2&app=com.tosan.dara.tosan&app_ver=1.0.0&X-cliv=fiid-4.7.1&delete=true
2020-10-20 23:29:52.922886+0330 dara[1314:192670] 6.34.0 - [Firebase/Analytics][I-ACS031010] Tracking view controller. Class, ID: RNNSideMenuController, -3628088477171312217
2020-10-20 23:29:52.922950+0330 dara[1314:192670] 6.34.0 - [Firebase/Analytics][I-ACS031013] Screen view event not logged. App is not active.
2020-10-20 23:29:52.922978+0330 dara[1314:192670] 6.34.0 - [Firebase/Analytics][I-ACS031006] View controller already tracked. Class, ID: RNNSideMenuController, -3628088477171312217
2020-10-20 23:29:52.923168+0330 dara[1314:192671] 6.34.0 - [Firebase/Analytics][I-ACS031010] Tracking view controller. Class, ID: RNNComponentViewController, -3628088477171312216
2020-10-20 23:29:52.923222+0330 dara[1314:192671] 6.34.0 - [Firebase/Analytics][I-ACS031013] Screen view event not logged. App is not active.
2020-10-20 23:29:52.923292+0330 dara[1314:192671] 6.34.0 - [Firebase/Analytics][I-ACS031006] View controller already tracked. Class, ID: RNNComponentViewController, -3628088477171312216
2020-10-20 23:29:53.136728+0330 dara[1314:192675] 6.34.0 - [Firebase/Analytics][I-ACS031006] View controller already tracked. Class, ID: RNNComponentViewController, -3628088477171312216
2020-10-20 23:29:53.324276+0330 dara[1314:192671] 6.34.0 - [Firebase/InstanceID][I-IID014007] Successfully deleted GCM server registrations on app reset
2020-10-20 23:29:53.324846+0330 dara[1314:192671] 6.34.0 - [Firebase/Installations][I-FIS002001] -[FIRInstallationsIDController installationWithValidAuthTokenForcingRefresh:0], appName: __FIRAPP_DEFAULT
2020-10-20 23:29:53.325396+0330 dara[1314:192671] 6.34.0 - [Firebase/Installations][I-FIS002000] -[FIRInstallationsIDController createGetInstallationItemPromise], appName: __FIRAPP_DEFAULT
2020-10-20 23:29:53.350505+0330 dara[1314:192675] 6.34.0 - [Firebase/InstanceID][I-IID020000] Register request to https://fcmtoken.googleapis.com/register content: X-osv=14.0.1&device=5483082389867869039&X-scope=*&plat=2&app=com.tosan.dara.tosan&app_ver=1.0.0&X-cliv=fiid-4.7.1&sender=398151505418&X-subtype=398151505418&appid=dbAoN1EVVUmpj3Vgj8-70_&gmp_app_id=1:398151505418:ios:fe36dc08007c241fb171f3
2020-10-20 23:29:53.799729+0330 dara[1314:192677] 6.34.0 - [Firebase/InstanceID][I-IID014001] Token fetch successful, token: dbAoN1EVVUmpj3Vgj8-70_:APA91bGaSrdaY161589O1w6SGWM5FTN4N193sBZCQ3satxtU8c9IECCX6u_Sa4YwIEpld6DFKiGeGCRrUmdLLBgQDhO85gGRv0h9rQj4ThR8H70L5bE5W4RoH6pYHWfAXdX6e8fSPJdq, authorizedEntity:<PHONE_NUMBER>18, scope:*
2020-10-20 23:29:53.816889+0330 dara[1314:192675] 6.34.0 - [Firebase/InstanceID][I-IID003010] Successfully fetched default token.
2020-10-20 23:29:53.817001+0330 dara[1314:192675] 6.34.0 - [Firebase/InstanceID][I-IID003008] Got default token dbAoN1EVVUmpj3Vgj8-70_:APA91bGaSrdaY161589O1w6SGWM5FTN4N193sBZCQ3satxtU8c9IECCX6u_Sa4YwIEpld6DFKiGeGCRrUmdLLBgQDhO85gGRv0h9rQj4ThR8H70L5bE5W4RoH6pYHWfAXdX6e8fSPJdq
2020-10-20 23:29:54.069255+0330 dara[1314:192673] 6.34.0 - [Firebase/Analytics][I-ACS031010] Tracking view controller. Class, ID: RNNComponentViewController, -3628088477171312215
2020-10-20 23:29:54.069323+0330 dara[1314:192673] 6.34.0 - [Firebase/Analytics][I-ACS031013] Screen view event not logged. App is not active.
2020-10-20 23:29:54.069352+0330 dara[1314:192673] 6.34.0 - [Firebase/Analytics][I-ACS031006] View controller already tracked. Class, ID: RNNComponentViewController, -3628088477171312215
2020-10-20 23:29:56.871 [warn][tid:com.facebook.react.JavaScript] Usage of "messaging().registerDeviceForRemoteMessages()" is not required. You only need to register if auto-registration is disabled in your 'firebase.json' configuration file via the 'messaging_ios_auto_register_for_remote_messages' property.
2020-10-20 23:29:56.883705+0330 dara[1314:192651] 6.34.0 - [Firebase/Installations][I-FIS002000] -[FIRInstallationsIDController createGetInstallationItemPromise], appName: __FIRAPP_DEFAULT
2020-10-20 23:29:56.884552+0330 dara[1314:192651] 6.34.0 - [Firebase/Installations][I-FIS002001] -[FIRInstallationsIDController installationWithValidAuthTokenForcingRefresh:0], appName: __FIRAPP_DEFAULT
2020-10-20 23:29:56.894817+0330 dara[1314:192671] 6.34.0 - [Firebase/Installations][I-FIS002000] -[FIRInstallationsIDController createGetInstallationItemPromise], appName: __FIRAPP_DEFAULT
2020-10-20 23:29:56.895309+0330 dara[1314:192671] 6.34.0 - [Firebase/Installations][I-FIS002001] -[FIRInstallationsIDController installationWithValidAuthTokenForcingRefresh:0], appName: __FIRAPP_DEFAULT
2020-10-20 23:29:56.897427+0330 dara[1314:192651] 6.34.0 - [Firebase/Installations][I-FIS002000] -[FIRInstallationsIDController createGetInstallationItemPromise], appName: __FIRAPP_DEFAULT
2020-10-20 23:29:56.899348+0330 dara[1314:192651] 6.34.0 - [Firebase/Installations][I-FIS002001] -[FIRInstallationsIDController installationWithValidAuthTokenForcingRefresh:0], appName: __FIRAPP_DEFAULT
2020-10-20 23:29:56.914153+0330 dara[1314:192671] 6.34.0 - [Firebase/Messaging][I-FCM017000] Topic subscription request: sender=dbAoN1EVVUmpj3Vgj8-70_:APA91bGaSrdaY161589O1w6SGWM5FTN4N193sBZCQ3satxtU8c9IECCX6u_Sa4YwIEpld6DFKiGeGCRrUmdLLBgQDhO85gGRv0h9rQj4ThR8H70L5bE5W4RoH6pYHWfAXdX6e8fSPJdq&app=com.tosan.dara.tosan&device=5483082389867869039&app_ver=1.0.0&X-gcm.topic=/topics/general&X-scope=/topics/general
2020-10-20 23:29:56.917463+0330 dara[1314:192670] 6.34.0 - [Firebase/Messaging][I-FCM017000] Topic subscription request: sender=dbAoN1EVVUmpj3Vgj8-70_:APA91bGaSrdaY161589O1w6SGWM5FTN4N193sBZCQ3satxtU8c9IECCX6u_Sa4YwIEpld6DFKiGeGCRrUmdLLBgQDhO85gGRv0h9rQj4ThR8H70L5bE5W4RoH6pYHWfAXdX6e8fSPJdq&app=com.tosan.dara.tosan&device=5483082389867869039&app_ver=1.0.0&X-gcm.topic=/topics/mobileBank_general&X-scope=/topics/mobileBank_general
2020-10-20 23:29:57.004731+0330 dara[1314:192670] 6.34.0 - [Firebase/Analytics][I-ACS031006] View controller already tracked. Class, ID: RNNComponentViewController, -3628088477171312215
2020-10-20 23:29:58.671027+0330 dara[1314:192671] 6.34.0 - [Firebase/InstanceID][I-IID003012] Provisioning profile has specifically provisioned devices, most likely a Dev profile.
2020-10-20 23:29:58.671117+0330 dara[1314:192671] 6.34.0 - [Firebase/InstanceID][I-IID003013] APNS Environment in profile: development
2020-10-20 23:29:58.673086+0330 dara[1314:192671] 6.34.0 - [Firebase/InstanceID][I-IID023000] Info is not found in Keychain. OSStatus: -25300. Keychain query: {
2020-10-20 23:29:59.055255+0330 dara[1314:192675] 6.34.0 - [Firebase/Messaging][I-FCM004003] Successfully subscribed to topic /topics/mobileBank_general
2020-10-20 23:29:59.055852+0330 dara[1314:192675] 6.34.0 - [Firebase/Messaging][I-FCM004003] Successfully subscribed to topic /topics/general
2020-10-20 23:30:01.248946+0330 dara[1314:192651] 6.34.0 - [Firebase/Analytics][I-ACS002001] APMExperimentAlarm fired
2020-10-20 23:30:01.249112+0330 dara[1314:192651] 6.34.0 - [Firebase/Analytics][I-ACS002003] APMExperimentAlarm canceled
2020-10-20 23:30:01.261309+0330 dara[1314:192673] 6.34.0 - [Firebase/Analytics][I-ACS002002] APMExperimentAlarm scheduled to fire in approx. (s): 14399.98781180382
2020-10-20 23:30:02.302967+0330 dara[1314:192651] 6.34.0 - [Firebase/Analytics][I-ACS002002] Engagement timer scheduled to fire in approx. (s): 3600
2020-10-20 23:30:02.315960+0330 dara[1314:192670] 6.34.0 - [Firebase/Analytics][I-ACS023051] Logging event: origin, name, params: auto, _vs, {
2020-10-20 23:30:02.325628+0330 dara[1314:192673] 6.34.0 - [Firebase/Analytics][I-ACS023072] Event logged. Event name, event params: _vs, {
2020-10-20 23:30:05.572785+0330 dara[1314:192675] 6.34.0 - [Firebase/Analytics][I-ACS002001] Measurement timer fired
2020-10-20 23:30:05.573002+0330 dara[1314:192675] 6.34.0 - [Firebase/Analytics][I-ACS002003] Measurement timer canceled
2020-10-20 23:30:05.583599+0330 dara[1314:192651] 6.34.0 - [Firebase/Analytics][I-ACS900001] Downloading data. Host: https://app-measurement.com/config/app/1:398151505418:ios:fe36dc08007c241fb171f3?platform=ios&app_instance_id=A7F3B076DA104D7C96EAD6F0C0AACCCF&gmp_version=60900
2020-10-20 23:30:06.455767+0330 dara[1314:192670] 6.34.0 - [Firebase/Analytics][I-ACS901006] Received SSL challenge for host. Host: https://app-measurement.com/config/app/1:398151505418:ios:fe36dc08007c241fb171f3?platform=ios&app_instance_id=A7F3B076DA104D7C96EAD6F0C0AACCCF&gmp_version=60900
2020-10-20 23:30:06.725978+0330 dara[1314:192670] 6.34.0 - [Firebase/Analytics][I-ACS029014] Successfully parsed a configuration. Version:<PHONE_NUMBER>496339
2020-10-20 23:30:06.741927+0330 dara[1314:192670] 6.34.0 - [Firebase/Analytics][I-ACS023105] Event is not subject to real-time event count daily limit. Marking an event as real-time. Event name, parameters: _f, {
2020-10-20 23:30:06.750581+0330 dara[1314:192670] 6.34.0 - [Firebase/Analytics][I-ACS012018] Saving bundle. size (bytes): 323
2020-10-20 23:30:06.751765+0330 dara[1314:192675] 6.34.0 - [Firebase/Analytics][I-ACS023116] Bundle added to the upload queue. BundleID, timestamp (ms): 1,<PHONE_NUMBER>557
2020-10-20 23:30:06.767324+0330 dara[1314:192675] 6.34.0 - [Firebase/Analytics][I-ACS023087] User property set. Name, value: _lte, 1
2020-10-20 23:30:06.768840+0330 dara[1314:192675] 6.34.0 - [Firebase/Analytics][I-ACS023087] User property set. Name, value: _se, 1
2020-10-20 23:30:06.774475+0330 dara[1314:192670] 6.34.0 - [Firebase/Analytics][I-ACS012018] Saving bundle. size (bytes): 379
2020-10-20 23:30:06.775290+0330 dara[1314:192670] 6.34.0 - [Firebase/Analytics][I-ACS023116] Bundle added to the upload queue. BundleID, timestamp (ms): 2,<PHONE_NUMBER>557
2020-10-20 23:30:06.792920+0330 dara[1314:192670] 6.34.0 - [Firebase/Analytics][I-ACS012018] Saving bundle. size (bytes): 379
2020-10-20 23:30:06.793910+0330 dara[1314:192670] 6.34.0 - [Firebase/Analytics][I-ACS023116] Bundle added to the upload queue. BundleID, timestamp (ms): 3,<PHONE_NUMBER>305
2020-10-20 23:30:06.803883+0330 dara[1314:192675] 6.34.0 - [Firebase/Analytics][I-ACS023039] Measurement data sent to network. Timestamp (ms), data:<PHONE_NUMBER>802, <APMPBMeasurementBatch: 0x2834f52d0>
2020-10-20 23:30:06.811795+0330 dara[1314:192675] 6.34.0 - [Firebase/Analytics][I-ACS900000] Uploading data. Host: https://app-measurement.com/a
2020-10-20 23:30:07.148526+0330 dara[1314:192651] 6.34.0 - [Firebase/Analytics][I-ACS901006] Received SSL challenge for host. Host: https://app-measurement.com/a
2020-10-20 23:30:07.386265+0330 dara[1314:192668] 6.34.0 - [Firebase/Analytics][I-ACS023044] Successful upload. Got network response. Code, size: 204, -1
2020-10-20 23:30:07.389029+0330 dara[1314:192673] 6.34.0 - [Firebase/Analytics][I-ACS002002] Measurement timer scheduled to fire in approx. (s): 9.996587991714478
2020-10-20 23:30:07.420426+0330 dara[1314:192673] 6.34.0 - [Firebase/Analytics][I-ACS002003] Measurement timer canceled

hmm i'm not able to reproduce. I'm able to get an APNS token after calling registerForRemoteNotification at a later time.
Can you file a customer support issue or send me your sample code at my email<EMAIL_ADDRESS>so we can investigate more on that.

@chliangGoogle I'm working on creating a new project for debugging, but during the process I realized that I used one modules called RNRestart that restart my application in my splash screen. I removed restarting my application and firebase starts working but I also realized that my Firebase token at first run and the second run is different , does it seem to be normal ?
Of course I'm not sure that removing my restart modules solved the problem may be some sort of race condition happened suddenly.

@chliangGoogle Excuse me...Are there any cases that cachedTokenIfAvailable return a token but cachedTokenInfos return nil in first fresh install app?

@shayantabatabaee the latest version of SDK should fix it. Can you update your cocoapod and try it again?
@trungnguyen1791 What kind of issue you running into? If it's a different one, please file a separate PR.

@shayantabatabaee the latest version of SDK should fix it. Can you update your cocoapod and try it again?
@trungnguyen1791 What kind of issue you running into? If it's a different one, please file a separate PR.

Thanks for your help, updating the sdk fix my problem, so I close the issue


Fix references to cvp dirs

Change Summary
Correct CI references to AVD directories instead of CVP.

Not needed


GO Package vulnerabilities in helm 3.9.3 release

On upgrading our Helm version from 3.8.2 to 3.9.3 we noticed many GO package related vulnerabilities. Please, let us know by when we can expect these to be fixed.

Can see this still seems to remain in rc1
CVE-2022-23806


ASIM NetworkSession schema parser with its sample data and tester files for Palo Alto Cortex Data Lake

Change(s):

Added ASIM NetworkSession schema parser for Palo Alto Cortex Data Lake based on CEF data

Reason for Change(s):

Initial version ASIM NetworkSession Parser

Version Updated:

Initial version

Testing Completed:

Yes

Checked that the validations are passing and have addressed any issues that are present:

Yes

Hi @niralishah-crest,
Thank you for raising Pull Request with us! We will review the Pull Request and get back to you by shortly. Thanks

Hi @niralishah-crest, please check comments above from @vakohl and act accordingly. Thanks

Hi @niralishah-crest,
To follow up appropriately, we would appreciate some indication of the timeframe for these changes. Thanks

Hi @niralishah-crest, please act on @vakohl's comments. Thanks

Hi @niralishah-crest,
We're waiting for an update on this. Thanks

Hi @niralishah-crest,
A few changes were suggested by @vakohl 3 weeks back. Could you please make those changes and update this request accordingly? Thanks

Hi @niralishah-crest,
We look forward to hearing back from you. Thanks

Hi @niralishah-crest, please update on above pending comments. Thanks

Hi @niralishah-crest,
Please work on above comment.
Thanks

We wanted to check on the status of PR #9126. PR is pending for more than 30 days. Please let us know if you need any assistance to review this PR. Per our standard operating procedures if no response is received in the next 7 business days, we will close this PR. Thank you for your cooperation.

@v-atulyadav
Sorry for the inconvenience.
We are unable to get chance to fix the suggested changes.
But now we are working on it and will update the PR with the fix of suggested changes by next week. So please do not close this PR.
Thanks.

Noted @jayeshprajapaticrest. Thanks

Noted @niralishah-crest. Thanks

@v-atulyadav @vakohl
We have addressed all review comments.
Thanks

Thanks @niralishah-crest.

Hi @niralishah-crest,
There are some changes that Varun has suggested, please take a look at them. Thanks

Hi @niralishah-crest,
We're waiting for an update on this. Thanks

Hi @niralishah-crest, please check comments above from @vakohl and act accordingly. Thanks

Hi @niralishah-crest, please act on above comments. Also check for branch conflicts. Thanks

Hi @niralishah-crest,
There are some changes that Varun has suggested, please take a look at them. Thanks

Hi @niralishah-crest,
Please work on above comment. Also look for a branch conflicts. Thanks


Upgrade the version from 3.2.5 to 3.3.0.

Coverage remained the same at 23.044% when pulling f930436067d006eefc753db64db2aa804de28ebd on feature/version_change into baf40004171bb8e6d1b4ac653992e6686eadf3f1 on master.

Coverage remained the same at 23.044% when pulling f930436067d006eefc753db64db2aa804de28ebd on feature/version_change into baf40004171bb8e6d1b4ac653992e6686eadf3f1 on master.

Coverage remained the same at 23.044% when pulling f930436067d006eefc753db64db2aa804de28ebd on feature/version_change into baf40004171bb8e6d1b4ac653992e6686eadf3f1 on master.


Create 'Think reuse before build' principle

This could potentially be merged with #100

Closing in favour of already opened #100


Update README.md

Punctuation error corrected

This is not a punctuation error. It's just a difference of opinion on the oxford comma.


ReadHandle does not preserve Data signature

ReadHandle._on_interest function currently transmits a Data packet like this:
https://github.com/JonnyKong/NDN-Repo/blob/47b62cbab776a4b6480c741d8b6c4d09ba96a2a8/src/handle/read_handle.py#L33
It constructs a Data packet from Name, MetaInfo, and Content, but does not preserve original Signature.
Generally, repo may be deployed on a node that does not possess producer's signing key. Signing the Data with a different key breaks application trust model.

A new function get_original_packet_value is added to NDNApp class, which may be helpful.

Fixed with https://github.com/JonnyKong/NDN-Repo/commit/b77e9c5c91ad3942a51b0a442ce0130de3226ab2.


The r-base package is inconsistent with the rest of conda-forge packages

The use of the jinja variable {{ native }} prevents the pinning script to issue PRs to fix the different pinnings used in the package. We probably will not be able to use the same pinnings onb Windows because we don't have any control over the msys2 packages used there, but we could at least get the Linux and OS X version in sync with the rest of the stack so users can install Python and R packages in teh same env.

Fixed in #5


When using F360 component references, ACDC4Robot does not export unique links

Problem
I have a design that uses reusable components (i.e. the leg part is reusable for both left and right sides).
In Fusion360, my robot has this hierachy:
robot
|-leg:1
|-body:1
|-leg:2
Fusion360 imports components with their basename, but to differentiate them, appends a :<ID> to the name.
When ACDC4Robot exports the URDF file, the name used for the links/joints do not include the unique identifier. i.e
    <link name="leg">
        <inertial>
   ...
    <link name="leg">
        <inertial>

instead of
    <link name="leg:1">
        <inertial>
   ...
    <link name="leg:2">
        <inertial>

This causes a failure in the UDRF import for tools such as PyBullet, RViz, etc.
Solution
Add component IDs to the exported link/joint names
Information
Platform: Fusion360 2.0.20754 arm64 [Native] MacOS
Python: 3.13
pybullet: 3.2.6

Your are right. :<ID> is the id for occurrence in Fusion360 and I just remove all the suffix when exporting URDF.
But I suggest you make occurrence independent by right click it and manually rename the occurrence using identifier.
Or, just comment s = re.sub(r':.*$', '', s) at ACDC4Robot/core/utils.py will solve your problem.

Your are right. :<ID> is the id for occurrence in Fusion360 and I just remove all the suffix when exporting URDF.
But I suggest you make occurrence independent by right click it and manually rename the occurrence using identifier.
Or, just comment s = re.sub(r':.*$', '', s) at ACDC4Robot/core/utils.py will solve your problem.


CloudSQL New BP Ext Rule for maintenance window cloudsql/BP_EXT/2023_001

Add new rule for CloudSQL - cloudsql/BP_EXT/2023_001

LGTM. Thanks for the PR


start analyzer on different port

I need to run two analyzers for the released and local versions of my package. With this change I can start them on different ports.
I also updated webpack and related deps

:tada: This PR is included in version 2.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Creating abnormalAnatomicalEntity phenotypes from FBBT for downstream tools

Flybase annotates abnormal anatomical entities with FBBT terms; downstream tools need to be able to distinguish FBBT terms from their phenotypes, and need a term for "abnormal eye". Can we find out from FlyBase if they would consider to host a component here in this repo that reads Flybase annotations from the database and automatically creates  corresponding phenotype terms (plus mappings to FBBT terms) here, ideally in the FBcv IRI namespace?

Based on an old spreadsheet (Sep 2018) Gil made me, 2880 FBbt terms have been used in phenotype curation, maybe a few more now.
Can I just clarify what you want to do?
So there would be 'abnormal X' terms in the FBcv namespace, but these would not be incorporated into FBcv or dpo? Would these terms form their own ontology? Would this ontology import FBbt?
We would also need an ID range set aside and some mechanism for creating new terms automatically when an FBbt term is used in phenotype curation for the first time.
What do you mean by 'mappings', will the phenotype terms not be automatically mapped by using FBbt terms in the logical definitions?

Where these abnormal terms life we have not yet decided. This are the considerations:

We want to be able to compare phenotype terms across species to integrate curated data from FlyBase with say data from WormBase
So we need a phenotype term wherever a phenotype is annotated
FlyBase has these, as you say 3K annotations against FBBT terms
To enable comparison between a WormBase phenotype and a fly phenotype, downstream tools have been generating their own weird flybase phenotype ontologies, see for example here, and in particular check the IRIs.
The hope would be that FlyBase would agree hosting all those weird abnormal anatomy fly phenotypes themselves. This would look like this:

A script pulls all FlyBase fbbt annotations and writes them to a table, like so:

anatomy
quality

FBBT:001
PATO:001

FBBT:002
PATO:002

A script then adds identifiers according to a prescribed scheme (that I already have implemented for ZP and XPO).

defined_class
anatomy
quality

FBCV:001
FBBT:001
PATO:001

FBCV:002
FBBT:002
PATO:002

Then we use the abnormalAnatomicalEntity pattern (uPheno) to generate an owl file. So each generated FBCV term is simply connected to it FBBT: term using the usual has part o inheres in boilerplate. FBBT terms would be imported from FBBT.
That OWL file is then imported into DPO (ideally), or, if this is not wanted by FlyBase, offered as a separate artefact in the DPO repository..
I understand that given the size, FlyBase might simply not want to integrate these terms into dpo (which would massively increase in size).

Thanks for the clarification.
Those FBbt_00000028PHENOTYPE style IRIs are horrible!
There isn't currently anything greater than FBcv:1000000, so we could allocate FBcv:1000000 to FBcv:1009999 for this (and more later if needed).
I don't see any problem with keeping these terms on the dpo repo, but we wouldn't want to integrate them into dpo as they will not be used for curation at FlyBase and, as you say, will massively bloat the ontology.
Do you already have scripts to do what you need or would this require some input from FlyBase?

Basically what we need to figure out is whether we can merge this file into the non-flybase-releases of dpo; This would mean they show up on OLS, etc.
My hole business here is: Once uPheno gets out, with all phenotypes across all species, people will start annotating to it; this will potentially include the fbbt phenotypes. It will be confusing to have the terms show up in the context of uPheno, but not in the context of dpo. So the ideal solution for me would be this:

DPO officially contains the abnormal anatomical entity phenotypes, so all its release files do too (including simple OWL and OBO). All of these are marked with a subset (abnormal_anatomy).
FBCV imports, instead of what it does now, a subset of DPO-simple, which first removes the abnormal anatomy terms.
This means FBCV remains exactly as it is now.

This would ensure:

No one creates fly terms elsewhere, so the namespace is still managed by the people best suited for it (FlyBase)
Anatomical phenotypes are kept up to date (and not go stale elsewhere, which means wrong subsumptions and outdated mappings to Flybase annotations)
Fly phenotypes are interoperable with other species, especially human.

(yes once the approach is agreed, I will implement everything with @dosumis)

@dosumis @Clare72 says that FBBT:001 could mean that the physical entity is affected, or a processes/function in/of FBBT:001 is affected. Is it safe to map FBBT:001 annotations from FlyBase to the abnormalAnatomicalEntity pattern in this way? Or do you see potential pitfalls?


Changing CSS/"Theming" support?

I'm very excited by the prospect of using CSS to style my Android application. For the app I'm working on, users are able to select a "theme" which changes the color and appearance of a variety of elements within the activity.
I'm wondering if it would be possible to implement the theming behavior by passing the path to the themed CSS file to the PixateFreestyle.init initializer. This could be implemented by adding an alternate form to the initializer like PixateFreestyle.init(this, 'my_theme.css'). Is that something that the project would be interested in supporting? If so, I can work on a pull request.

Of course!
This can be useful. We'll review your PR once you push it.
Thanks


Need to automate restarts stateful/stateless

Since sometimes we need to start/restart mutliple AMs/actors at once we should automate this process so only a minimal input is required.

As one part essentially clean-restart can be performed with the steps in Install Control Framework section.
SITE="<SITE_NAME>"
INVENTORY="fabric-hosts"
PLAYBOOK="site.yml"
LIMIT="${SITE}_head"

# Stop and clean

ansible-playbook -i ${INVENTORY} ${PLAYBOOK} --limit ${LIMIT} --tags "software-cf-authority-teardown"

# Updates (eg. aggregate-ads are copied) should be done and
# variables should be adjusted (eg. software versions) as described
# in the referenced doc above

# Deploy and start

ansible-playbook -i ${INVENTORY} ${PLAYBOOK} --limit ${LIMIT} --tags "software-cf-cert"
ansible-playbook -i ${INVENTORY} ${PLAYBOOK} --limit ${LIMIT} --tags "software-cf-aggregate-ads"
ansible-playbook -i ${INVENTORY} ${PLAYBOOK} --limit ${LIMIT} --tags "software-cf-directory"
ansible-playbook -i ${INVENTORY} ${PLAYBOOK} --limit ${LIMIT} --tags "software-cf-checkout"
ansible-playbook -i ${INVENTORY} ${PLAYBOOK} --limit ${LIMIT} --tags "software-cf-inventory"
ansible-playbook -i ${INVENTORY} ${PLAYBOOK} --limit ${LIMIT} --tags "software-cf-authority-setup"
ansible-playbook -i ${INVENTORY} ${PLAYBOOK} --limit ${LIMIT} --tags "software-cf-authority-setup-docker"
ansible-playbook -i ${INVENTORY} ${PLAYBOOK} --limit ${LIMIT} --tags "software-cf-authority-setup-kafka"
ansible-playbook -i ${INVENTORY} ${PLAYBOOK} --limit ${LIMIT} --tags "software-cf-authority-run-docker"

#
# Stop containers
#
INVENTORY="fabric-hosts"
PLAYBOOK="site.yml"
LIMIT="salt-hn"
TAGS="software-cf-authority-stop-containers"
ansible-playbook -i ${INVENTORY} ${PLAYBOOK} --limit ${LIMIT} --tags ${TAGS}

#
# Stop and remove containers (removal of volumes and/or images can be added)
#
INVENTORY="fabric-hosts"
PLAYBOOK="site.yml"
LIMIT="salt-hn"
TAGS="software-cf-authority-stop-remove-containers"
ansible-playbook -i ${INVENTORY} ${PLAYBOOK} --limit ${LIMIT} --tags ${TAGS}

#
# Start containers
#
INVENTORY="fabric-hosts"
PLAYBOOK="site.yml"
LIMIT="salt-hn"
TAGS="software-cf-authority-start-containers"
ansible-playbook -i ${INVENTORY} ${PLAYBOOK} --limit ${LIMIT} --tags ${TAGS}

#
# Redeploy ads
#
INVENTORY="fabric-hosts"
PLAYBOOK="site.yml"
LIMIT="salt-hn"
TAGS="software-cf-aggregate-ads-redeploy"
ansible-playbook -i ${INVENTORY} ${PLAYBOOK} --limit ${LIMIT} --tags ${TAGS}

There are two things I want to incorporate. Basically there should be a restart clean/stateful and with and without model update and I believe these can be independent. I.e. you can have a stateful restart with model update. The other dimension is automatically cleaning up any stale slivers if it is a clean restart - this seems like a must - CF should call a 'close' on all slivers touching on the AM /actor being restarted. We need to discuss some more but if we implement these two things, restarts will become a lot less painful, esp. if model updates can be done statefully.
My sense is stateful model update is actually OK. Yes - something has changed in the model, we can undelegate, redelegate (all this means is unmerging/merging AM ADM graph from broker without touching existing reservations). We already have all the info we need to close reservations stored in Postgres, so model update doesn't affect it. I expect the vast majoriy of reasons why we restart AMs will be minor model updates and as such we can make them painless to the users.

Steps to follow for stateful restart with model updates for an AM:

Un-delegate resources for the AM from the Broker
Create a file inside the AM container at the location: /usr/src/app/reload.model
Stop the AM container
Copy the new ARM
Start the AM container
After recovery, the temporary file would be deleted by CF
Re-delegate resources from the AM to the Broker


Update Query service methods for fleetctl compatibility

Service methods and associated datastore methods for OsqueryQuery YAML.

Pushed changes to this consistent with https://github.com/kolide/fleet/pull/1674/files

Note this PR was massively updated to combine the refactoring of packs and queries, as these are highly intertwined.

Also note:
We enforce referential integrity on the references from packs to queries with foreign key constraints in the DB, but our current strategy with heterogenous target types prevents us from doing the equivalent there. I think we probably want to enforce it for targets as well, but that will require changing the join table strategy for targets. Perhaps work for a later PR.


BottomNavigationBarItem doesn't have activeIcon property.

(https://github.com/flutter/flutter/blob/master/examples/flutter_gallery/lib/demo/material/bottom_navigation_demo.dart)
In flutter gallery demo source code, it uses activeIcon property in Bottombar item,
but now I can't see activeIcon property in Bottombar item as well. (Build error)
I hope to use it,  the demo looks so cool.
Thanks flutter.

show the output of flutter doctor
I think your flutter is not updated, try updating it

So what is the new method of setting active icon in the newest versions?

@zoechi Thanks for the info. When I changed channel to dev some other plugins didn't work properly like cached_network_image. When is this changes gonna be merged to beta channel?

@gunhansancar If you are currently having issues with plugins/packages on dev then you will still have those problems when beta is updated.  I would encourage you to file issues agains the package/plugin owners.

... or check that you have the latest version of plugins/packages.

@jonahwilliams I filed the issue on that particular plugin.
@zoechi I think I have up-to-date plugins and packages.
My question is which channel should I supposed to use dev or beta? Or if I put it in different way should plugin owners support dev channel?

@gunhansancar Without knowing your situation I cannot say whether beta or dev is better, but the fundamental tradeoff of a more frequently updated branch is less stability.  Not necessary in the sense of bugs - dev branches are tested quite thoroughly as well - but in the sense of things (apis, implementations) changing.


Fetching delay

Hello!
Thanks for this app, it's cool!
I'm faced with an interesting case: I have teku node in archive mode with data-storage-archive-frequency: 8192 and it can answer to some API really long time. As example:
:~$ time curl -s localhost:3500/eth/v1/beacon/states/1701967/committees > /dev/null

real    9m20.688s
user    0m0.019s
sys     0m0.003s

:~$ time curl -s localhost:3500/eth/v1/beacon/states/1701957/committees > /dev/null

real    10m13.902s
user    0m0.017s
sys     0m0.009s

The thing is that chaind updates blocks longer than new blocks appear  in that case. As result chaind starts to lag behind the head more and more.
For fast resolving this issue, I made some non-production ready changes : tried to use worker pool for simultaneous requests for speeding up query process just after restart the service.
How about to implement something similar to upstream? I can help with PR if it's interesting for you and you can help me with the architect approach how to implement it.

I have had a think about this, and there area  few issues.
There is a concern that overloading the beacon chain node in this way will cause more harm than good, as it will cause duplication of work as the same path is trodden for each block in parallel.  In general you really should run teku in full archive mode if you want to obtain data from it; the time/space tradeoff for doing so very heavily favours giving teku more space to reduce the time taken to return blocks.
A separate concern is around the loose coupling of modules, and the impact that out-of-order fetching of blocks may have.  Although the idea of missed slots was good in theory, in practice it has resulted in confusion where a slot without data in chaind could be a missing block, or just a block that hasn't been gathered yet.  This makes additional modules such as the finalizer and summarizer much harder to manage, so the next version of chaind will do away with missed slots and instead stop at the first failure to obtain a block.  This provides a much higher level of surety that if block 100 is present in the DB then all blocks prior to that are either also present in the DB or not in the chain, which in turn makes finalizing a far less error-prone process.
Ultimately, the simplicity of keeping chaind sequential for fetching data is worth the requirement that the beacon node keeps a complete state log.  If you are still seeing issues after running teku in full archive mode then some sort of batching or grouping system may be possible, but I'd rather avoid it due to the additional complexity it would bring.

Thank you for clear explanation!
So I close this case due to architecture approach


Misc/Yauaa.Netstandard - [https://github.com/OrbintSoft/yauaa.netstan…

Misc/Yauaa.Netstandard - https://github.com/OrbintSoft/yauaa.netstandard
This library provides a semantic user agent parsing and extract all relevant informations (browser, operating system, device name, etc..)

The library provides the same features as DeviceDetector.NET, but in my opinion is better because it is not limited to a static database of regular expressions but provides a semantic parsing.
It can extract a lot more attributes, see here for output doc.
Anyway that is just a list of predefined attributes, you can add custom rules and attributes to parse custom user agents, this is the only .NET library that is able to do that.
The library provides a lot more features like binary serialization, test rules, etc...
Really I can't see this project too small, but yes I understand that there is still very low community usage and and we have a lot work to do.
Anyway the project is very actively maintained.
I am spending a lot of time to update and improve documentation and explain all features.
I hope community will approve this project.

Sorry, but the community hasn't rallied behind this project to get it included. Thanks for your contribution.


Fix #42494

As discussed, just make sure I didn't break any suggest behaviour with this. It makes more sense to set the state before revealing, since setting the state will trigger layout, which influences how reveal works.
Fixes #42494

@joaomoreno Can you fix merge conflicts. Unsure if we still want this for Feb or better March?

@jrieken Resolved. Up to you 👍

Taking the risk ;-)

It broke stuff.


unhandled rejections fix in angular 1.6

Angular 1.6 invoke an error when rejected promise are unhandled.
In addition, there is no need to return anything in promise's resolve and rejection callbacks. then method that accept callback methods as parameters, returns promise. Therefore $q.reject(resp) is unneded and cause unhandled promise rejection error.

+1

Agree this should go in, but I'm currently seeing 8 failed tests involving other possibly-unhandled rejection errors. They can most likely be fixed in the spec setup itself, but I can't merge this until they pass. You mind taking a look?

Now auth methods return HttpPromise instead of promise with a result of callback (resolve/reject) method. Test should be fine.

+1

where the failing tests ever addressed @MariuszHenn ?
if so, can we merge @booleanbetrayal ?

As You see in my last comment (4 Oct 2017), all test passes in my local build.

Merged!


Upgrade AGP to 7

Used https://github.com/cortinico/kotlin-android-template for local testing. It appears to work fine.
EDIT: Now that AGP 7 drops support for Java 8, at some point I think we also need to move towards Java 11.

This PR is pending on the outcome of https://github.com/detekt/detekt/discussions/4130

To unblock this can we not just restrict the tests to running on JDK 11? We already limit which JDKs can be used to run the Android tests by blocking JDK 16+ due to GSON incompatibility (used by AGP - I haven't tested if that imcompatibility is fixed in AGP 7):
internal fun skipIfAndroidEnvironmentRequirementsUnmet() = when {
    !isAndroidSdkInstalled() -> Skip.Yes("No android SDK.")
    getJdkVersion() >= 16 -> Skip.Yes("Android 4.1.3 & 4.2.1 don't run on JDK 16 or higher")
    else -> Skip.No
}

I agree with you, contingent on the assumption that users are building at least JDK 11 for Android Projects. Maybe we should announce that we can guarantee compatibility with the latest AGP release?

Maybe we should announce that we can guarantee compatibility with the latest AGP release?

It's essentially already described on this page:
https://detekt.github.io/detekt/compatibility.html
Once we bump AGP to 7.x, we're implicitly dropping support for AGP 4.x
That means that is safe to assume that, if you're using Detekt 1.20.x (or whichever version this PR will land into), you're on AGP 7.x and JDK 11.
If you're not, you're on your own essentially ¯_(ツ)_/¯

6 months since agp 7.0 was launched. I'm ok dropping support for agp 4.


Document convenient development of UI files.

@grobie @samstarling does this make things clearer (and work for you)?

Perfect, thanks! :+1:

Oh, and regarding whether it works - I'm pretty sure it's something I'm doing wrong, but I'll investigate properly tomorrow and let you know.


Holding alt while double clicking to open properties - no longer working

Description
This feature was originally requested in https://github.com/files-community/Files/issues/3105, and added in https://github.com/files-community/Files/pull/4441, but it was removed in https://github.com/files-community/Files/pull/4365. The removal looks to be by mistake.
Steps To Reproduce

Hold Alt
While holding it, double click a file or folder

Expected behavior
The properties should window should open, but instead, it opens the file or folder.
Files Version
<IP_ADDRESS>
Windows Version
Windows 10 21H1 19043.1237
Relevant Assets
No response

I don't know if this was ever supported but you can access properties from the alt + enter shortcut.


Avoid restarting vite devserver when env file changes

Currently when the application env file changes, the vite devserver restarts on another port. Not sure why it uses another port but we don't want it to restart anyway, we want to maintain control over env vars for this application.
To do:

[x] Add test

@apedroferreira There's a minor issue in the test that I've seen before in other tests, is that queries don't reload when the env file changes. With the current functionality this is not a huge problem because to change the env file you'd have to blur the window and window focus causes a revalidation for all queries. This currently doesn't happen in playwright and they don't support hiding/showing the tab yet. We'll have to fix this issue at some point when we start altering .env files from the UI.
second to note is that the env file gets loaded from disk on every query call, this is wasteful and I'd like to centralize all env file logic for functions and rest queries so that it loads only once and notifies on changes. Will look into this after merging https://github.com/mui/mui-toolpad/pull/2062

@apedroferreira There's a minor issue in the test that I've seen before in other tests, is that queries in the canvas don't reload when the env file changes. With the current functionality this is not a huge problem because to change the env file you'd have to open your code editor and browser window focus causes a revalidation for all queries. Playwright doesn't support an API to simulate hiding/showing the browser tab yet. We'll have to fix this issue at some point though when we start altering .env files from the UI. second to note is that the env file gets loaded from disk on every query call, this is wasteful and I'd like to centralize all env file logic for functions and rest queries so that it loads only once and notifies on changes. Will look into this after merging #2062

Ok, we should look into loading the env data from memory and also making sure it's always up to date in queries no matter what. Thanks for looking into it, but let me know if I should create an issue for this / look into it instead if it helps!

Playwright doesn't support an API to simulate hiding/showing the browser tab yet.

I have this in the rest-basic tests:
 // Make sure switching tabs does not close query editor
  const newTab = await context.newPage();
  await newTab.bringToFront();
  await page.bringToFront();
  await expect(newQueryEditor).toBeVisible();

It might not do exactly what a real browser does though, if I remember correctly.


Refactor receive_packet to remove duplication

Coverage increased (+0.03%) to 80.496% when pulling db436ed901083d2183f26a149f3af5fa95bc04a4 on shssoichiro:refactor-finalize-frame into 0f56dfea39440d2eac4c267cf8e41976c03608ba on xiph:master.


Fix orthologues list strain filter

Description
Triticum aestivum has the strain group value set to triticum_aestivum which is causing them to be filtered from getting displayed in the orthologues list.
Views affected
http://wp-np2-1d.ebi.ac.uk:42228/Triticum_turgidum/Gene/Compara_Ortholog?db=core;g=TRITD2Bv1G183370;r=2B:540943210-541159134;t=TRITD2Bv1G183370.1#list_no_ortho
Related JIRA Issues (EBI developers only)
https://www.ebi.ac.uk/panda/jira/browse/ENSWEB-6474

Please use SPECIES_PRODUCTION_NAME instead of lc($species) - we're trying to get rid of these, not create more!

@ens-ap5 - That's done


Oracle "FROM all_tables WHERE  owner = (select user from dual)" query

Problem:
typeorm-model-generator run following query:
 SELECT
   NULL AS TABLE_SCHEMA,
   TABLE_NAME
FROM all_tables
WHERE  owner = (select user from dual)

This returns 0 results for me, because these tables owner's is not equal to current user - these tables are owned by DBA and I'm working with read-only user.
Solution: add option to specify owner(s).
Workaround: hardcode correct value in node_modules/typeorm-model-generator/dist/src/drivers/OracleDriver.js (replace (select user from dual) with 'YOUR_OWNER').

from user_constraints should be replaced with from all_contraints owner (...) WHERE owner.owner = 'YOUR_OWNER'

@Ginden can you please clarify. I am trying to get this package working for an oracle database.
user_constraints is also used in many joins, should we change user_constraints to all_constraints owner (...) where owner.owner = 'YOUR_NAME' in every join also?
Also what should replace the ellipsis inside the parenthesis?
TIA

ok I got it working. I had to change four SQL strings in OracleDriver.js. They start at lines 25, 40, 174, and 205.

@goughjo02 Hi, could you provided which files you changed, maybe a pr or diff links will helpful.


detecting feedback loops - part of the translation from OT to gen~. using a graph colouring algorithm. essential for a feedback loop between 2+ modules

~current progress: can detect feedback loops (known as 'cycles' in graphs) between specific inlets and outlets, BUT as many ops/modules have multiple inlets and outlets, my current algorithm can't detect cycles between one module to another.~

@grrrwaaa I wrote an algorithm for graph colouring. its likely very inefficient, but it seems to work for now. It will print all of the arcs which should have a gen [history] object inserted between them.
the code is at branch develop/findCycles.js
You can run it using either
node findCycles.js <full path to a scene.json file>
# or run it without an argument for it to just run on scene_rich2.json
node findCycle.js

bump this thread. We decided yes to adding a history=true or history=false _prop to the OT spec in order to indicate a cable as either feedback or non-feedback cable in both the patcher scripting as well as the VR space.

ready. see https://github.com/worldmaking/mischmasch/blob/develop/historify.js


isolatedDeclarations should not have warning for functions that have no return statements

🔎 Search Terms
isolatedDeclaration
🕗 Version & Regression Information
5.5.0
⏯ Playground Link
https://www.typescriptlang.org/play/?isolatedDeclarations=true&ts=5.5.0-dev.20240426#code/KYDwDg9gTgLgBAMwK4DsDGMCWEWIBQCUcA3gL5A
💻 Code
export function f() {}

🙁 Actual behavior
Function must have an explicit return type annotation with --isolatedDeclarations. (9007)
🙂 Expected behavior
No error
Additional information about the issue
Functions with no return statements can be easily inferred as type void, so there is no need to give this warning.

Not doing this was intentional; a function without a return may not always be void.
declare function fail(): never;
export function f() {
	fail();
}
export const g = () => { fail(); }

Is:
export declare function f(): void;
export declare const g: () => never;

Playground Link

Correct error for function expressions, but not function declarations - declarations won't infer never

#58331 is indiscriminate in what it affects; if we want to allow this for function declarations only, that may be possible, but it sure seems like an extra inconsistency just to avoid 5 characters...

hmm, I didn't think of never, so the function expression part is wrong. But I find it annoying to write : void for obviously clear function declarations.

Discussed and we don't want to make it untenable to, in the future, change the rules around function declaration return type inference. For example, it's maybe preferable that
function dofail() {
  Debug.fail("oops");
}

have an inferred return type of never (as it would if written as a function expression) rather than void.


Frame freezes whilst try display/save high resolution frame

With reference to - https://picamera.readthedocs.io/en/release-1.13/api_array.html#picamera.array.PiArrayOutput.truncate
Here we are trying to save one high-resolution image from the capture() function (every 15 frames) while running the low-resolution stream on the capture_continuous (), we find that the program freezes when trying to switch to the high-resolution image. How does one fix this?
Our readings show that we can change the resolution directly however it freezes in the same manner, refer to the above link (15.1):

From the image we see that one image is saved for the low resolution after which the resolution is changed to save another image.
context - we are trying to run a low-resolution preview in real-time and when the user presses a button a high-resolution image is saved.
We need fast fps for the preview hence the low res during the preview and then save a high res image.
We need the low resolution capture_continuous function in order for the preview to work.
import picamera.array
from picamera import PiCamera
from picamera.array import PiRGBArray
from picamera.exc import PiCameraValueError
import time
import cv2
import numpy as np
from datetime import datetime

camera = PiCamera()
camera.resolution = (320,240)
camera.framerate = 30

highResCap = PiRGBAArray(camera)  # new 4-byte-per-pixel version above
lowResCap = PiRGBAArray(camera, size=(320, 240))

lowResStream = camera.capture_continuous(lowResCap, format="bgra", use_video_port=True, splitter_port=2, resize=(320, 240))
time.sleep(2.0)
print("done warming up")
lowres_fc = 0
rawCaptureHiRes = PiRGBArray(camera, size=(3280, 2464))
while True:
    lrs = next(lowResStream)
    lrFrame = lrs.array
    lowres_fc+=1
    print("High res frame gen time: ",datetime.now().time())
    if lowres_fc%15==0:
        camera.resolution = (3280,2464)
        camera.capture(rawCaptureHiRes, splitter_port=1, format="bgr", use_video_port=True)
        print("GOT HIGH RES", str(rawCaptureHiRes.array.shape))
        img2 = cv2.cvtColor(rawCaptureHiRes.array, cv2.COLOR_BGR2GRAY)
        cv2.imwrite("testhrs.jpg", img2)
        camera.resolution = (320,240)
        print("High res frame save time: ",datetime.now().time())
    cv2.imshow('lores', lrFrame)
    if cv2.waitKey(1) == 27:
        break

The sensor produces frames in one of a number of modes, and each mode can achieve a different maximum frame rate. See https://picamera.readthedocs.io/en/latest/fov.html#sensor-modes
When you request a high res frame, the sensor will stop, switch to the higher resolution/lower frame rate mode, capture the high res frame, stop the sensor again, switch to the lower resolution/higher frame rate mode, and then resume preview/low res capture.
You could use sensor_mode to force the sensor to stay in one mode all the time, but that will limit you on max frame rate (or max resolution).


Forgot password PF wallet

O forgot the password to do transfer. Os the same oficial 12 words?

Hello @bksbruno
Thanks for reaching out to us.
The 12-word recovery phrase is not the encrypt password but it lets you recover the wallet.
To know how to recover the wallet please refer to #9292 .
To know more about the passwords please read this article: https://support.bitpay.com/hc/en-us/articles/360018366012-BitPay-Products-and-Their-Passwords
Please let us know if you have any additional questions.
Kind regards.

@bksbruno
if you haven't recovered your wallet, i can do it dm me<EMAIL_ADDRESS>


page preview for all internal links

For internal links, show a preview of the relevant page on hover. (Exactly like #2, but not just in the backlinks section.)

Related to #2

As per https://github.com/binyamin/eleventy-garden/discussions/71#discussion-3765981, I'm considering this one "out of scope".