iOS Push Notifications Not Received (from FF Triggers) After Apple Org. Account Migration - "Untitled" Certificates & "Sent to 0 Devices

Hi FlutterFlow Community,

I'm facing a persistent issue with iOS push notifications for my app "FindRosi" after migrating my individual Apple Developer account to an Organization account and would greatly appreciate any insights.

Current Situation:

Account: Migrated from an individual Apple Developer account to an Organization account. The Team ID surprisingly remained the same.
Backend & Push: Using Firebase and FCM. A .p8 APNs Auth Key is correctly configured in Firebase for the new Organization team.
Successful Test: Sending a test push notification directly from the Firebase Console to my test iPhone's FCM token works perfectly. The notification arrives.
Problem: Notifications triggered by FlutterFlow's standard Cloud Functions (listening to ff_user_push_notifications collection) are not received on iOS devices. When I use FlutterFlow's "Manually trigger push notification" test feature, it reports "Sent to 0 devices."
App Startup Logs: When the app starts, I see these logs which might be relevant:
- WARN: ⚠️ The appUserID passed to logIn is the same as the one already cached. No action will be taken. (From RevenueCat, likely unrelated but noting it)
- GTMSessionFetcher 0xXXXXXXXXX (https://.../addFcmToken) was already running (Indicates a potential issue with how/when addFcmToken is called)

Xcode Issues (which I suspect are related):

"Untitled" Certificates: In Xcode -> Settings -> Accounts -> [My Apple ID] -> Select "{=[My Organization Team] -> "Manage Certificates...", my newly created Development and Distribution certificates for the Organization team are often listed as "Untitled".
"No App ID" for Push Console: In my app target's "Signing & Capabilities" tab, if I click the info button for "Push Notifications", it says: "no app IDs: Register an App ID with the Push Notifications capability enabled..." – even though the capability is enabled for my main Bundle ID in the Apple Developer Portal

Troubleshooting So Far:

Multiple recreations of all certificates (Dev & Dist) and Provisioning Profiles (Dev & App Store) specifically for the Organization team and the correct App ID.
Ensured "Push Notifications" capability is enabled for the App ID in the Developer Portal and linked to the .p8 APNs key.
Using "Automatically manage signing" in Xcode with the Organization team selected.
Deleted Derived Data.
Verified all Bundle Identifiers.
Confirmed APNs Auth Key (Key ID, Team ID) in Firebase is correct for the Organization.
Temporarily opened Firestore Security Rules for ff_user_push_notifications.
Re-deployed the standard FlutterFlow push notification Cloud Functions.

Given that a direct FCM send from the Firebase Console works, I'm leaning towards an issue in the chain involving how FlutterFlow's backend functions fetch tokens or construct/send the FCM message, potentially compounded by a code signing/provisioning profile mismatch Xcode perceives due to the "Untitled" certificates, despite settings in the Developer Portal. The "Sent to 0 devices" from FF's test tool is a key indicator.

Has anyone experienced similar "Untitled" certificates in Xcode or push notification failures specifically from FF's backend triggers (while direct FCM console sends work) after an Apple Developer account type change? Any advice on what to check next or how to resolve the "Untitled" certificate display and the "Sent to 0 devices" issue would be immensely helpful!

Thanks,
Benedikt