You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-06-22] [$250] [Sentry: APP-8BM] HybridApp iOS NSInvalidArgumentException nil object in RCTNetworking prioritizedHandlers #92413
-[RCTNetworking prioritizedHandlers]
-> -[RCTNetworking handlerForRequest:]
-> -[RCTNetworking sendRequest:responseType:...]
-> __RCTAppSetupDefaultModuleFromClass_block_invoke_2
-> +[NSArray arrayWithObjects:count:] (nil object at index 3)
Suspected cause
RCTNetworking builds the prioritized handlers array with a nil entry — likely a race or a handler that failed to register on HybridApp startup or during an in-flight network request.
Reproduction
Unknown deterministically — crashes during RCTNetworking request dispatch on HybridApp iOS. See linked Sentry events.
Related
Sibling Sentry IDs (if any): none identified
Prior GH issues: none
Production scan: releases 9.3.89, 9.3.90, 9.3.91 (2026-06-02)
On HybridApp iOS, the first network request dispatched after certain bridge/module-registry states fatally crashes with NSInvalidArgumentException ("nil object at index 3") instead of completing the request.
Root cause
The crash is not in RCTNetworking itself — that frame is just where the lazy handler list is first materialized. -[RCTNetworking handlerForRequest:] (node_modules/react-native/Libraries/Network/RCTNetworking.mm:223-267) calls -[RCTNetworking prioritizedHandlers] (RCTNetworking.mm:269-296), which on first use invokes the _handlersProvider block to build and cache the handler array:
That _handlersProvider is the block installed in RCTAppSetupDefaultModuleFromClass — reached because -[RCTReactNativeFactory getModuleInstanceFromClass:] (RCTReactNativeFactory.mm:193) falls through to it for RCTNetworking. The block is __RCTAppSetupDefaultModuleFromClass_block_invoke_2 in the stack trace, and it builds the default handler list like this:
1 - Index 3 (BlobModule) can resolve to nil. The first three entries are created with +new and are never nil. The fourth, [moduleRegistry moduleForName:"BlobModule"], is a registry lookup — it resolves RCTBlobManager, which registers as RCT_EXPORT_MODULE(BlobModule) (node_modules/react-native/Libraries/Blob/RCTBlobManager.mm:45). -[RCTModuleRegistry moduleForName:] returns nil whenever that module is not (yet) instantiable: during HybridApp's OldDot↔NewDot bridge handoff the module registry is torn down/rebuilt, so there is a window where the network stack is alive and accepting requests but BlobModule resolves to nil. This matches the report exactly: iOS-only, hybrid_app, non-deterministic, "nil object at index 3".
2 - The list is built with an Objective-C array literal, which is fatal on nil.@[ … ] compiles to +[NSArray arrayWithObjects:count:] (the bottom frame in the trace), which raises NSInvalidArgumentException the instant any element is nil. So a transiently-missing BlobModule turns a recoverable "one fewer handler" situation into a hard crash. Note the sibling image-loader block directly above (RCTAppSetupUtils.mm:92-99) is nil-safe by construction — it only ever puts +new instances (RCTBundleAssetImageLoader, RCTGIFImageDecoder) into its literal. The networking block is the only one that mixes a fallible registry lookup into a literal.
Proposed fix
Guard the BlobModule lookup at its source via a patch-package patch, matching the existing convention in patches/react-native/. Build the defaults in a nil-tolerant NSMutableArray and append BlobModule only when present:
// node_modules/react-native/Libraries/AppDelegate/RCTAppSetupUtils.mm:101-112 (after)
} elseif (moduleClass == RCTNetworking.class) {
return [[moduleClass alloc]
initWithHandlersProvider:^NSArray<id<RCTURLRequestHandler>> *(RCTModuleRegistry *moduleRegistry) {
NSArray *URLRequestHandlerModules =
extractModuleConformingToProtocol(moduleRegistry, @protocol(RCTURLRequestHandler));
// moduleForName:"BlobModule" can be nil during HybridApp bridge transitions.// Build with a mutable array and skip a nil BlobModule instead of crashing the// @[...] literal with a nil object at index 3 (Sentry APP-8BM).NSMutableArray<id<RCTURLRequestHandler>> *defaultHandlers = [NSMutableArrayarrayWithObjects:
[RCTHTTPRequestHandler new], [RCTDataRequestHandler new], [RCTFileRequestHandler new], nil];
id<RCTURLRequestHandler> blobModule = (id<RCTURLRequestHandler>)[moduleRegistry moduleForName:"BlobModule"];
if (blobModule) {
[defaultHandlers addObject:blobModule];
}
return [defaultHandlers arrayByAddingObjectsFromArray:URLRequestHandlerModules];
}];
}
[NSMutableArray arrayWithObjects: a, b, c, nil] is safe because the three +new entries are guaranteed non-nil and the trailing nil is just the varargs terminator. Ship it as patches/react-native/react-native+0.83.1+038+fix-networking-nil-blob-handler-APP-8BM.patch, e.g.:
Add the matching entry to patches/react-native/details.md (Reason: prevents NSInvalidArgumentException when BlobModule is transiently nil during HybridApp bridge transitions; E/App issue: #92413; Sentry: APP-8BM).
Why this approach
Fixing it at the source — the provider block where the nil is introduced — is strictly better than filtering nils downstream in RCTNetworking.prioritizedHandlers, because the literal crashes beforeRCTNetworking ever sees the array, so a downstream guard would never run. The change is also behavior-preserving: when BlobModule is present the handler set is byte-for-byte identical (same order, same priorities), and when it is transiently absent the app simply lacks a blob handler for that brief window instead of crashing — RCTNetworking.handlerForRequest: already tolerates a shorter list and the cache is rebuilt on the next bridge. This is the same patch-package mechanism Expensify already uses for native RN crash fixes such as react-native+0.83.1+037+fix-deadlock-APP-7B2.patch and …+019+fix-crash-when-deleting-expense.patch, and it mirrors the nil-safe construction already used by the adjacent image-loader provider block. The App's own custom handler (ios/NewExpensify/OriginImageRequestHandler.mm, handlerPriority 4) is appended through URLRequestHandlerModules and is unaffected.
Please re-state the problem that we are trying to solve in this issue.
HybridApp iOS can crash while React Native is dispatching a network request. The fatal exception is NSInvalidArgumentException from +[NSArray arrayWithObjects:count:] because RCTNetworking builds its prioritized URL request handler list with a nil object.
In RN 0.83.1, RCTAppSetupDefaultModuleFromClass() creates the default iOS RCTNetworking handler provider with an Objective-C array literal. The fourth entry is a nullable module-registry lookup:
That lookup asks for BlobModule, and RCTModuleRegistry can return nil when neither the bridge nor TurboModule registry can provide the module at that moment:
So the trigger is a network request reaching RCTNetworking.handlerForRequest(), the mechanism is prioritizedHandlers invoking the provider before it can sort or filter handlers, and the impact is that the Objective-C array literal crashes as soon as the BlobModule slot is nil:
This matches Sentry's nil object at index 3: the first three entries are freshly allocated HTTP/data/file handlers, while index 3 is the nullable BlobModule lookup. App's custom dependency-provider handlers are appended after this default array, so they cannot be the nil object that crashes this stack.
What changes do you think we should make in order to solve the problem?
Add a React Native patch for RCTAppSetupUtils.mm so the iOS networking handler list is built without placing the nullable BlobModule lookup inside an array literal.
The patch should:
Create the default handler list from the non-null RCTHTTPRequestHandler, RCTDataRequestHandler, and RCTFileRequestHandler instances.
Read id blobModule = [moduleRegistry moduleForName:"BlobModule"].
Append blobModule only when it conforms to RCTURLRequestHandler.
Append URLRequestHandlerModules from extractModuleConformingToProtocol(...) after that, preserving the existing dependency-provider extension point.
This preserves normal HTTP/data/file requests, keeps blob URL handling when BlobModule is registered, and turns the missing/transient blob module case into "no blob handler available" instead of crashing unrelated requests. App already ships RN fixes through patch-package, including HybridApp crash fixes, and the patch runner applies App patches in HybridApp installs:
Use the next available RN patch filename, for example patches/react-native/react-native+0.83.1+038+fix-ios-networking-nil-blob-handler.patch, and document it in patches/react-native/details.md.
Scope boundaries: files touched are patches/react-native/react-native+0.83.1+038+fix-ios-networking-nil-blob-handler.patch for node_modules/react-native/Libraries/AppDelegate/RCTAppSetupUtils.mm inside the RCTNetworking default-module provider, plus patches/react-native/details.md for patch documentation. Platforms affected are iOS native and HybridApp iOS through RN networking initialization. Do not change JS request code, backend/API behavior, Android networking, RCTBlobManager behavior when the module exists, or App's custom OriginImageRequestHandler.
What alternative solutions did you explore? (Optional)
Filtering nil handlers inside RCTNetworking.prioritizedHandlers is too late because the crash happens while the provider constructs the array it returns.
Creating a new fallback RCTBlobManager instance would avoid the nil array entry, but it risks splitting blob storage from the registered JS BlobModule. Skipping only the missing blob handler is narrower and keeps blob support unchanged whenever the real module exists.
Treating this as a private Mobile-Expensify-only HybridApp issue is also weaker here. The crash line is in public React Native 0.83.1 source, and the public App repo already has the patch-package path that HybridApp builds use for RN patches.
Confidence: High — the Sentry stack trace matches the React Native source frame-for-frame.
What is the root cause of that problem?
The crash happens inside React Native core, in the RCTNetworking URL-request-handlers provider that ships with RN 0.83.1.
When RCTNetworking dispatches its first network request, it lazily builds and caches its list of request handlers in -[RCTNetworking prioritizedHandlers], which invokes the handlersProvider block defined in RCTAppSetupUtils.mm. That block returns an Objective-C array literal of four handlers:
index 0: [RCTHTTPRequestHandler new]
index 1: [RCTDataRequestHandler new]
index 2: [RCTFileRequestHandler new]
index 3: [moduleRegistry moduleForName:"BlobModule"] <-- can be nil
An array literal @[...] compiles to +[NSArray arrayWithObjects:count:]. On HybridApp iOS, [moduleRegistry moduleForName:"BlobModule"] sometimes returns nil (the BlobModule / RCTBlobManager is not present in the module registry at the moment the first request triggers handler construction). Inserting nil into the literal throws NSInvalidArgumentException — "attempt to insert nil object at index 3" — which is fatal.
This explains every reported symptom: the exact exception, "nil object at index 3", the __RCTAppSetupDefaultModuleFromClass_block_invoke_2 frame (the 2nd handler-provider block), the prioritizedHandlers → handlerForRequest: → sendRequest: chain, and why it's non-deterministic (it only fires on the first in-flight request when BlobModule happens to be unregistered/not-yet-ready).
Code evidence
The handler array is built here (local: App/node_modules/react-native/Libraries/AppDelegate/RCTAppSetupUtils.mm lines 103–112, unpatched RN 0.83.1):
This is core RN — none of App's 37 existing react-native+0.83.1+* patches touch this file, so the local copy matches upstream.
What changes do you think we should make in order to solve the problem?
Make the handler array construction nil-safe via a new patch-package patch on react-native (e.g. patches/react-native/react-native+0.83.1+038+fix-crash-APP-8BM.patch).
Instead of placing [moduleRegistry moduleForName:"BlobModule"] directly inside the array literal, fetch it into a local variable first and only append it when it is non-nil (build a NSMutableArray with the three always-available handlers, conditionally add the BlobModule, then arrayByAddingObjectsFromArray: the rest). This eliminates the fatal exception regardless of why BlobModule is momentarily missing, and matches the precedent of App's other Sentry-driven RN native patches (e.g. react-native+0.83.1+037+fix-deadlock-APP-7B2.patch).
Because HybridApp iOS builds consume the App submodule's patched react-native pod, this App-repo patch fixes the HybridApp crash without any change required elsewhere.
What alternative solutions did you explore? (Optional)
Find why BlobModule is unregistered on HybridApp (a Mobile-Expensify native host / startup-race investigation). Worth doing as a follow-up to address the underlying cause, but the defensive patch above stops the fatal crash immediately and is the lower-risk, App-only fix. The nil-guard is correct to keep even if the registration issue is later resolved, since RN treats a missing BlobModule as non-fatal everywhere else.
Next Steps for Contributor+ team: To accept:@MelvinBot implement this to create a draft PR. To refine:@MelvinBot <your feedback> To reject: Explain why you are rejecting Melvin's proposal.
Sorry for missing your earlier comment. I'd like to request a standard payment for this issue - $250. Although it doesn't require video evidence, the fix lies in a low-level layer, and it took time to investigate deeper and do related research on React Native to move it forward
Activity
melvin-bot commentedon Jun 2, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @DylanDylann (
External)[-][Sentry: APP-8BM] HybridApp iOS NSInvalidArgumentException nil object in RCTNetworking prioritizedHandlers[/-][+][$250] [Sentry: APP-8BM] HybridApp iOS NSInvalidArgumentException nil object in RCTNetworking prioritizedHandlers[/+]melvin-bot commentedon Jun 2, 2026
Job added to Upwork: https://www.upwork.com/jobs/~022061885267670586222
trasnake87 commentedon Jun 2, 2026
Proposal
On HybridApp iOS, the first network request dispatched after certain bridge/module-registry states fatally crashes with
NSInvalidArgumentException("nil object at index 3") instead of completing the request.Root cause
The crash is not in
RCTNetworkingitself — that frame is just where the lazy handler list is first materialized.-[RCTNetworking handlerForRequest:](node_modules/react-native/Libraries/Network/RCTNetworking.mm:223-267) calls-[RCTNetworking prioritizedHandlers](RCTNetworking.mm:269-296), which on first use invokes the_handlersProviderblock to build and cache the handler array:That
_handlersProvideris the block installed inRCTAppSetupDefaultModuleFromClass— reached because-[RCTReactNativeFactory getModuleInstanceFromClass:](RCTReactNativeFactory.mm:193) falls through to it forRCTNetworking. The block is__RCTAppSetupDefaultModuleFromClass_block_invoke_2in the stack trace, and it builds the default handler list like this:There are two contributing factors:
1 - Index 3 (
BlobModule) can resolve to nil. The first three entries are created with+newand are never nil. The fourth,[moduleRegistry moduleForName:"BlobModule"], is a registry lookup — it resolvesRCTBlobManager, which registers asRCT_EXPORT_MODULE(BlobModule)(node_modules/react-native/Libraries/Blob/RCTBlobManager.mm:45).-[RCTModuleRegistry moduleForName:]returnsnilwhenever that module is not (yet) instantiable: during HybridApp's OldDot↔NewDot bridge handoff the module registry is torn down/rebuilt, so there is a window where the network stack is alive and accepting requests butBlobModuleresolves tonil. This matches the report exactly: iOS-only, hybrid_app, non-deterministic, "nil object at index 3".2 - The list is built with an Objective-C array literal, which is fatal on nil.
@[ … ]compiles to+[NSArray arrayWithObjects:count:](the bottom frame in the trace), which raisesNSInvalidArgumentExceptionthe instant any element is nil. So a transiently-missingBlobModuleturns a recoverable "one fewer handler" situation into a hard crash. Note the sibling image-loader block directly above (RCTAppSetupUtils.mm:92-99) is nil-safe by construction — it only ever puts+newinstances (RCTBundleAssetImageLoader,RCTGIFImageDecoder) into its literal. The networking block is the only one that mixes a fallible registry lookup into a literal.Proposed fix
Guard the
BlobModulelookup at its source via apatch-packagepatch, matching the existing convention inpatches/react-native/. Build the defaults in a nil-tolerantNSMutableArrayand appendBlobModuleonly when present:[NSMutableArray arrayWithObjects: a, b, c, nil]is safe because the three+newentries are guaranteed non-nil and the trailingnilis just the varargs terminator. Ship it aspatches/react-native/react-native+0.83.1+038+fix-networking-nil-blob-handler-APP-8BM.patch, e.g.:Add the matching entry to
patches/react-native/details.md(Reason: preventsNSInvalidArgumentExceptionwhenBlobModuleis transiently nil during HybridApp bridge transitions; E/App issue: #92413; Sentry: APP-8BM).Why this approach
Fixing it at the source — the provider block where the nil is introduced — is strictly better than filtering nils downstream in
RCTNetworking.prioritizedHandlers, because the literal crashes beforeRCTNetworkingever sees the array, so a downstream guard would never run. The change is also behavior-preserving: whenBlobModuleis present the handler set is byte-for-byte identical (same order, same priorities), and when it is transiently absent the app simply lacks a blob handler for that brief window instead of crashing —RCTNetworking.handlerForRequest:already tolerates a shorter list and the cache is rebuilt on the next bridge. This is the samepatch-packagemechanism Expensify already uses for native RN crash fixes such asreact-native+0.83.1+037+fix-deadlock-APP-7B2.patchand…+019+fix-crash-when-deleting-expense.patch, and it mirrors the nil-safe construction already used by the adjacent image-loader provider block. The App's own custom handler (ios/NewExpensify/OriginImageRequestHandler.mm,handlerPriority4) is appended throughURLRequestHandlerModulesand is unaffected.KJ21-ENG commentedon Jun 2, 2026
Proposal
Please re-state the problem that we are trying to solve in this issue.
HybridApp iOS can crash while React Native is dispatching a network request. The fatal exception is NSInvalidArgumentException from +[NSArray arrayWithObjects:count:] because RCTNetworking builds its prioritized URL request handler list with a nil object.
What is the root cause of that problem?
Expensify is on React Native 0.83.1:
App/package.json
Line 174 in 5e75aa0
In RN 0.83.1, RCTAppSetupDefaultModuleFromClass() creates the default iOS RCTNetworking handler provider with an Objective-C array literal. The fourth entry is a nullable module-registry lookup:
https://github.com/facebook/react-native/blob/v0.83.1/packages/react-native/Libraries/AppDelegate/RCTAppSetupUtils.mm#L101-L111
That lookup asks for BlobModule, and RCTModuleRegistry can return nil when neither the bridge nor TurboModule registry can provide the module at that moment:
https://github.com/facebook/react-native/blob/v0.83.1/packages/react-native/React/Base/RCTModuleRegistry.m#L32-L54
So the trigger is a network request reaching RCTNetworking.handlerForRequest(), the mechanism is prioritizedHandlers invoking the provider before it can sort or filter handlers, and the impact is that the Objective-C array literal crashes as soon as the BlobModule slot is nil:
https://github.com/facebook/react-native/blob/v0.83.1/packages/react-native/Libraries/Network/RCTNetworking.mm#L223-L229
https://github.com/facebook/react-native/blob/v0.83.1/packages/react-native/Libraries/Network/RCTNetworking.mm#L269-L278
This matches Sentry's nil object at index 3: the first three entries are freshly allocated HTTP/data/file handlers, while index 3 is the nullable BlobModule lookup. App's custom dependency-provider handlers are appended after this default array, so they cannot be the nil object that crashes this stack.
What changes do you think we should make in order to solve the problem?
Add a React Native patch for RCTAppSetupUtils.mm so the iOS networking handler list is built without placing the nullable BlobModule lookup inside an array literal.
The patch should:
This preserves normal HTTP/data/file requests, keeps blob URL handling when BlobModule is registered, and turns the missing/transient blob module case into "no blob handler available" instead of crashing unrelated requests. App already ships RN fixes through patch-package, including HybridApp crash fixes, and the patch runner applies App patches in HybridApp installs:
App/scripts/applyPatches.sh
Lines 27 to 32 in 5e75aa0
Use the next available RN patch filename, for example patches/react-native/react-native+0.83.1+038+fix-ios-networking-nil-blob-handler.patch, and document it in patches/react-native/details.md.
Scope boundaries: files touched are patches/react-native/react-native+0.83.1+038+fix-ios-networking-nil-blob-handler.patch for node_modules/react-native/Libraries/AppDelegate/RCTAppSetupUtils.mm inside the RCTNetworking default-module provider, plus patches/react-native/details.md for patch documentation. Platforms affected are iOS native and HybridApp iOS through RN networking initialization. Do not change JS request code, backend/API behavior, Android networking, RCTBlobManager behavior when the module exists, or App's custom OriginImageRequestHandler.
What alternative solutions did you explore? (Optional)
Filtering nil handlers inside RCTNetworking.prioritizedHandlers is too late because the crash happens while the provider constructs the array it returns.
Creating a new fallback RCTBlobManager instance would avoid the nil array entry, but it risks splitting blob storage from the registered JS BlobModule. Skipping only the missing blob handler is narrower and keeps blob support unchanged whenever the real module exists.
Treating this as a private Mobile-Expensify-only HybridApp issue is also weaker here. The crash line is in public React Native 0.83.1 source, and the public App repo already has the patch-package path that HybridApp builds use for RN patches.
MelvinBot commentedon Jun 2, 2026
Proposal
What is the root cause of that problem?
The crash happens inside React Native core, in the
RCTNetworkingURL-request-handlers provider that ships with RN 0.83.1.When
RCTNetworkingdispatches its first network request, it lazily builds and caches its list of request handlers in-[RCTNetworking prioritizedHandlers], which invokes thehandlersProviderblock defined inRCTAppSetupUtils.mm. That block returns an Objective-C array literal of four handlers:An array literal
@[...]compiles to+[NSArray arrayWithObjects:count:]. On HybridApp iOS,[moduleRegistry moduleForName:"BlobModule"]sometimes returnsnil(the BlobModule /RCTBlobManageris not present in the module registry at the moment the first request triggers handler construction). Insertingnilinto the literal throwsNSInvalidArgumentException— "attempt to insert nil object at index 3" — which is fatal.This explains every reported symptom: the exact exception, "nil object at index 3", the
__RCTAppSetupDefaultModuleFromClass_block_invoke_2frame (the 2nd handler-provider block), theprioritizedHandlers → handlerForRequest: → sendRequest:chain, and why it's non-deterministic (it only fires on the first in-flight request when BlobModule happens to be unregistered/not-yet-ready).Code evidence
The handler array is built here (local:
App/node_modules/react-native/Libraries/AppDelegate/RCTAppSetupUtils.mmlines 103–112, unpatched RN 0.83.1):RCTAppSetupUtils.mm(RN v0.83.1)It is invoked lazily, on a request, in
-[RCTNetworking prioritizedHandlers](local:App/node_modules/react-native/Libraries/Network/RCTNetworking.mm):RCTNetworking.mm(RN v0.83.1)This is core RN — none of App's 37 existing
react-native+0.83.1+*patches touch this file, so the local copy matches upstream.What changes do you think we should make in order to solve the problem?
Make the handler array construction nil-safe via a new
patch-packagepatch onreact-native(e.g.patches/react-native/react-native+0.83.1+038+fix-crash-APP-8BM.patch).Instead of placing
[moduleRegistry moduleForName:"BlobModule"]directly inside the array literal, fetch it into a local variable first and only append it when it is non-nil(build aNSMutableArraywith the three always-available handlers, conditionally add the BlobModule, thenarrayByAddingObjectsFromArray:the rest). This eliminates the fatal exception regardless of why BlobModule is momentarily missing, and matches the precedent of App's other Sentry-driven RN native patches (e.g.react-native+0.83.1+037+fix-deadlock-APP-7B2.patch).Because HybridApp iOS builds consume the App submodule's patched
react-nativepod, this App-repo patch fixes the HybridApp crash without any change required elsewhere.What alternative solutions did you explore? (Optional)
BlobModuleis unregistered on HybridApp (a Mobile-Expensify native host / startup-race investigation). Worth doing as a follow-up to address the underlying cause, but the defensive patch above stops the fatal crash immediately and is the lower-risk, App-only fix. The nil-guard is correct to keep even if the registration issue is later resolved, since RN treats a missing BlobModule as non-fatal everywhere else.Next Steps for Contributor+ team:
To accept:
@MelvinBot implement thisto create a draft PR.To refine:
@MelvinBot <your feedback>To reject: Explain why you are rejecting Melvin's proposal.
46 remaining items
melvin-bot commentedon Jun 25, 2026
@mallenexpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
mallenexpensify commentedon Jun 25, 2026
Payment Summary
Contributor+: @DylanDylann due $250 via NewDot
no tests were needed on PR
DylanDylann commentedon Jun 26, 2026
Sorry for missing your earlier comment. I'd like to request a standard payment for this issue - $250. Although it doesn't require video evidence, the fix lies in a low-level layer, and it took time to investigate deeper and do related research on React Native to move it forward
@mountiny Do you agree? ☝️
mountiny commentedon Jun 26, 2026
Yeah I think $250 here is appropriate @mallenexpensify
mallenexpensify commentedon Jun 26, 2026
@DylanDylann paid, summary updated above. Thx.
quinthar commentedon Jul 31, 2026
Approved $250 to @DylanDylann