Repository navigation
[Due for payment 2026-06-17] Upgrade Airship before RN 0.85 bump #92529
Description
Parent issue
Part of #91629 — must land before the main React Native 0.85 / Expo SDK 56 bump PR.
Background
Airship SDK must be upgraded on the current RN stack before the main version bump so push notification native code stays compatible with HybridApp.
Scope
- Bump Airship SDK to 26.5.0 in App and Mobile-Expensify (HybridApp parity)
- Update Android notification handling (
CustomAirshipExtender.java,ExpensifyNotificationProvider.java,PushNotificationManager.java) for Airship 26.5.0 API changes - Update iOS pods and Android
build.gradle/AndroidManifest.xmlas needed
Pull requests
- App: chore: upgrade airship to 26.5.0 #92497
- Mobile-Expensify: https://github.com/Expensify/Mobile-Expensify/pull/13960
Acceptance criteria
- App builds on iOS and Android
- HybridApp builds with Mobile-Expensify changes
- Push notifications are received and deep-link to the correct screen when tapped
- App launches without crashes on startup
- No new JS console errors
Notes
- Keep this PR focused — do not include the RN / Expo version bump here
Activity
3 remaining items
melvin-bot commentedon Jun 10, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.1-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-06-17. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Jun 10, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)melvin-bot commentedon Jun 15, 2026
@mallenexpensify Eep! 4 days overdue now. Issues have feelings too...
melvin-bot commentedon Jun 16, 2026
Payment Summary
Upwork Job
BugZero Checklist (@mallenexpensify)
QichenZhu commentedon Jun 17, 2026
BugZero Checklist:
[Contributor] The offending PR and associated issue have been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to the comment on the PR: N/A. Not a bug.
Link to the comment on the Issue: N/A.
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: N/A.
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Existing tests already cover this.
mallenexpensify commentedon Jun 18, 2026
Payment Summary
Contributor+: @QichenZhu due $250 via NewDot
trjExpensify commentedon Jun 19, 2026
approved $250 for @QichenZhu