Skip to content

fix: [SDK-5526] read Flutter Android log entries from content-desc - #60

Merged
fadi-george merged 2 commits into
mainfrom
fadi/sdk-5526
Oct 17, 2026
Merged

fadi-george merged 2 commits into
mainfrom
fadi/sdk-5526

Conversation

@fadi-george

@fadi-george fadi-george commented Oct 16, 2026 •

Copy link
Copy Markdown
Contributor

Description

getLogMessages() reads content-desc for Flutter on Android, so log assertions work for the Flutter demo there.

Details

Flutter on Android exposes non-editable text through content-desc, which leaves text empty. The Appium log helper read only getText(), so with the Flutter log view (OneSignal/OneSignal-Flutter-SDK, SDK-5526) every entry came back empty and expectOneNewLog timed out in spec 02. The content-desc read is gated on Flutter + Android, so other SDKs keep using getText() unchanged.

Tested with the Flutter log view branch:

  • Android 16 emulator: --spec=02 3/3, --spec=13 2/2, with log assertions executed
  • iPhone 17 simulator (iOS 26.2): --spec=02 3/3, --spec=13 2/2

🤖 Generated with Claude Code

…-desc

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…id log entries

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@fadi-george
fadi-george merged commit 6546779 into main Oct 17, 2026
2 checks passed
@fadi-george
fadi-george deleted the fadi/sdk-5526 branch October 17, 2026 00:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant