[Bug] Android Power Apps: Dataverse GetItem never returns; retrieveMultiple hangs after Code App navigation

Start by reproducing the published Code App on Power Apps for Android with @microsoft/power-apps 1.2.2 and 1.3.0, focusing on generated Service.get()/retrieveRecordAsync and retrieveMultiple calls after list-to-detail navigation. Compare isolated, serial, and concurrent requests with iOS or desktop; done means Android requests either settle successfully or surface an error without requiring an app restart.

Describe the bug

In a published Power Apps Code App running in Power Apps for Android (Play Store):

retrieveRecordAsync / generated Service.get() (GetItem) against a Dataverse row never returns. The same table's getAll / retrieveMultiple (list query) succeeds.

Concurrent retrieveMultiple calls hang indefinitely. The same calls complete successfully in parallel on iOS Power Apps (typically within 1–2 seconds).

Serial retrieveMultiple calls on related tables can succeed when the app is idle, but may hang after navigating to a detail screen. We measured successful Android responses of approximately 145–186 ms on an isolated diagnostics screen, yet observed a single child-table retrieveMultiple call hang for more than one minute after list → detail navigation.

The host does not reject the calls. The returned promises never resolve or reject. Closing and reopening the Power Apps app is the only workaround we found to reset the connector state.

The issue reproduces with:

@microsoft/power-apps 1.2.2
@microsoft/power-apps 1.3.0

iOS and desktop environments remain unaffected.

Steps to Reproduce

All steps performed in a published Power Apps Code App using Dataverse generated services (@microsoft/power-apps) on Power Apps for Android.

1. GetItem hang (reliable)

Call retrieveMultiple / getAll on a custom Dataverse table.
Verify the list query succeeds.

Call Service.get(id) / retrieveRecordAsync using one of the returned record IDs.

Observe that the promise never resolves or rejects (tested beyond 60 seconds).

2. Concurrent retrieveMultiple hang (reliable)

From a detail screen, execute several child-table queries simultaneously using Promise.all (activities, attachments, follows, etc.).
Observe:
Android: none of the requests complete.
iOS: all requests complete successfully.

3. Serial retrieveMultiple works until detail navigation (reliable)

On a diagnostics screen without the detail route mounted:
Execute one jobs-list retrieveMultiple.
Run three related-table retrieveMultiple calls sequentially.
Android completes successfully (~186 ms, ~145 ms, ~167 ms).
Navigate to a detail route using a parent record sourced from the list cache (no GetItem call).
After the detail header renders, execute a single retrieveMultiple against a child table (for example, Activities).

Observe:
Android: request hangs for more than one minute with no error.
iOS: request completes in approximately 1–2 seconds.

Service surface used
List operations: getAll() → retrieveMultiple
Item operations: get() → retrieveRecordAsync

Environment uses custom Dataverse tables with the coh_ publisher prefix and UserOwned ownership model.

Expected behavior

retrieveRecordAsync should return either the requested record or a surfaced error, consistent with iOS and desktop behavior.
retrieveMultiple should either:
return successfully,
return an error, or
fail fast if concurrency limits exist.
Navigation between screens should not permanently stall Dataverse read operations.

Actual behavior

GetItem (retrieveRecordAsync) hangs indefinitely with no error.
Concurrent retrieveMultiple requests hang indefinitely with no error.
After list → detail navigation, a later serial retrieveMultiple request against a related table can hang even though the same APIs previously succeeded in the same Android session.

Client-side timeouts do not cancel the underlying host operation. Starting additional requests after a timeout can worsen the issue by creating multiple hanging operations.

Screenshots or Error Messages

None.

No HTTP status code, SDK exception, host error, or Power Apps player notification is surfaced. The UI remains in a loading state because the promise never settles.

Environment information

Framework / Build Tools

React 19.2
Vite 7
TypeScript
@microsoft/power-apps 1.3.0
Also reproduced with 1.2.2
@microsoft/power-apps-vite 1.0.2
Code Apps CLI 0.12.0

Connections / Components

Dataverse
Generated services only (no direct HTTP calls from the UI)

Platforms

Desktop browser: related reads work correctly
iOS Power Apps: related reads work correctly, including parallel getAll
Android Power Apps:
list getAll works
GetItem hangs
concurrent getAll hangs
serial related getAll may hang after detail navigation

Deployment

Published Power Apps Code App
Single app where each deployment replaces the previous bundle

Additional context

The same Code App functions successfully in Power Apps for iOS, including Dataverse retrieveMultiple operations.
Android is not a complete failure scenario:
App launch works
Authentication works
List retrieval works
The failures appear isolated to specific Dataverse client operations and/or Android WebView connector interactions.
Upgrading @microsoft/power-apps from 1.2.2 to 1.3.0 did not resolve the issue.
Android device model: Samsung Galaxy S26+
Power Apps Android version: Latest / Current

Current workarounds

Avoid Service.get() / retrieveRecordAsync on Android.
Open records from existing list (getAll) results whenever possible.
Filtering getAll by ID was also observed to be fragile on detail screens.
Avoid overlapping retrieveMultiple operations on Android.
Avoid triggering child-table retrieveMultiple calls from Android detail screens.