[FR]: Add an origin marker to FIAM-generated NSUserActivity
Maintainers usually reply within 1 day
@mennahmustafaa is already working on this.
Since Nov 8, 2026.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 64/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- ios, objective-c
- Domain
- mobile
Research direction
Start with followURLWithSceneContinueUserActivity: in FirebaseInAppMessaging/Sources/Runtime/FIRIAMActionURLFollower.m (lines 225–240), where FIAM creates and forwards the activity. Check how the activity’s userInfo is populated and how this API is documented. Done means FIAM-created activities include a documented origin identifier that lets callers distinguish them from Universal Links.
Written by the indexing model from the issue text.
Description
Description
Since v13, FIAM prioritizes scene(_:continue:) for HTTP(S) action URLs.
Even ordinary web URLs that are not Universal Links are delivered as NSUserActivityTypeBrowsingWeb. There is currently no explicit marker to distinguish these FIAM-generated activities from actual Universal Links.
We need this distinction to open ordinary FIAM web URLs externally without also opening unsupported Universal Links.
Relevant implementation: followURLWithSceneContinueUserActivity: creates and forwards the activity without an origin identifier.
API Proposal
Add a documented FIAM origin identifier to userActivity.userInfo when FIAM creates the activity.
Firebase Product(s)
In-App Messaging
- Dominant language
- C++
- Stars
- 7k
- Forks
- 1.8k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 70
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from firebase/firebase-ios-sdk
-
api: analytics
Difficulty 4/5 3-5 days Newbie friendliness 35/100
firebase/firebase-ios-sdk#17075 ·
Maintainers usually reply within 1 day
-
api: firestore
Difficulty 4/5 3-5 days Newbie friendliness 43/100
firebase/firebase-ios-sdk#17073 ·
Maintainers usually reply within 1 day
-
RTDB: `.info` listen `onComplete` runs off the repo queue, so `infoSyncTree` is mutated from two threads (crash in `FSyncTree applyOperationHelper`)Possibly taken @paulb777 claimed this 3 days ago. Open
firebase/firebase-ios-sdk#17069 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
Firestore watch stream keeps an expired App Check token until the next Auth refresh (no-op App Check change listener in FirestoreClient)Possibly taken @dconeybe claimed this 5 days ago. Openapi: firestore
firebase/firebase-ios-sdk#17056 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
api: crashlytics
Difficulty 4/5 3-5 days Newbie friendliness 35/100
firebase/firebase-ios-sdk#17046 ·
Maintainers usually reply within 1 day
All issues in firebase/firebase-ios-sdk
Similar issues
-
feat
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Issue-Docs Needs-Triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
microsoft/winget-cli#6692 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
stratum-mining/sv2-tp#167 ·
Maintainers usually reply within 1 day
-
better error message bug low priority semantics strings
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day