From 4ec6ff2b38a8e5edc1f311716d417d1bdfb10486 Mon Sep 17 00:00:00 2001 From: Antonis Lilis Date: Tue, 6 Oct 2026 10:41:25 +0200 Subject: [PATCH] test(e2e): Re-enable iOS view_names assertion in captureMessage test The JS captureMessage event's `view_names` is set entirely in JS from the clean React Navigation `route.name`, matching the already-enabled Android assertion. The generated route-key hash referenced by the old TODO no longer appears, so re-enable the assertion with the clean route name. Closes #6844 Co-Authored-By: Claude Opus 4.8 --- .../e2e/tests/captureMessage/captureMessage.test.ios.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/samples/react-native/e2e/tests/captureMessage/captureMessage.test.ios.ts b/samples/react-native/e2e/tests/captureMessage/captureMessage.test.ios.ts index 7672dc8412..7ff741cba1 100644 --- a/samples/react-native/e2e/tests/captureMessage/captureMessage.test.ios.ts +++ b/samples/react-native/e2e/tests/captureMessage/captureMessage.test.ios.ts @@ -87,7 +87,7 @@ describe('Capture message', () => { app_start_time: expect.any(String), app_version: expect.any(String), in_foreground: expect.any(Boolean), - // view_names: ['ErrorsScreen-jn5qquvH9Nz'], // TODO: fix this generated hash should not be part of the name + view_names: ['ErrorsScreen'], }), }), }),