Timestamped event matching error failed to find matching element

[React-Native] — Fastlane screenshots, recorder throw «Timestamped Event Matching Error. » #12748

Question Checklist

• Updated fastlane to the latest version
• I read the Contribution Guidelines
• I read docs.fastlane.tools
• I searched for existing GitHub issues

Question Subject

Question about setting up the wanted screenshots with fastlane screenshots

Question Description

Alright, I was setting up my project with fastlane in order to generate screenshots for the release on the store. When I tried to update the textExample() function in [. ]UITest.swift using the Recorder , my simulator launched well, but when I clicked on any buttons, I got this error =>
Timestamped Event Matching Error: Failed to find matching element
I found many peoples with this issue but who weren’t doing a react native project.
Do you have any ideas about how to resolve it ?

The text was updated successfully, but these errors were encountered:

It seems like you have not included the output of fastlane env

To make it easier for us help you resolve this issue, please update the issue to include the output of fastlane env 👍

@MayeuldP Heyyy 👋 This sounds like its not related to your Fastfile but instead related to your UI tests. It sounds like you are trying to specific an element by name/key in your UI tests (that control the screenshots) and the element you are specifying by name/key doesn’t exist — either because its not on screen or its not configured properly.

I think that is all that I am able to help you since I cannot do much debugging on your UI tests 😔

@joshdholtz Hello, thank for your help, indeed, it worked for few components by adding testID=»identifier» as props.
However. for others elements, even if there’s a testID props, I got this as a return, app.otherElements.matching(random stuff) instead of app.buttons[«indetifier’] for example, so then, running fastlane screenshot doesnt work, and display that No matches found for Find: . Do I do something wrong with the testID ?

By the way, every time I run fastlane screenshots the app build every time again which is taking a long time, I tried to add derived_data_path : ./fastlane/DerivedDataPath and test_without_building true but didnt work.

Succeed to make it work for components, but still have troubles to use it for my TabNavigator even if I put
tabBarTestIDProps: < accessibilityLabel: ‘navigateProject’, testID: ‘navigateProject’ >, xCode doesn t find it.

@MayeuldP I think this is sadly a side effect of using an abstraction layer such as ReactNative 😔 I also have an RN app that writing snapshot stuff for was more difficult than it probably should have been just due to the way that RN creates its views. So it sounds like you are on the right track of getting things working 🙃

And setting a derived_data_path and test_without_building should have worked for making things build faster but again, this might be an RN thing? 😬

@joshdholtz Yeah indeed I succeed to make it works, concerning derived_data_path and test_without_building .
Concerning ReactNative, I think, it’s hard to make it work properly with fastlane. Do you guys plan to integrate fastlane for react-Native ?
Else, do you suggest or know, any tools for generate all the screenshots for a react-native app for itunes connect ?

Thanks for your help.

@MayeuldP We do try to support whatever our users are using and it seems like either RN is gaining popularity 😊 I would like to add more docs for RN and possibly some better onboarding in tools and such but there is also a fine line on how to manage our resources 🙃

That being said, I would love to hear all your pain points when integrating fastlane in RN 🙏 I have an RN app that I maintain but I have fastlane working but I probably have a different view on fastlane 😇

Is your main issue on just taking screenshots with RN? Or were there some other gotchas that you found?

Would be so cool indeed.
Yeah I was planing to use fastlane only for the screenshots. Well, actually, since there’s no documentation for RN on fastlane, I needed to go search for informations here and there on internet. There’s several tutorials about how managing release and automatic deployments, but never about the screenshots, since UI tests on Xcode for RN Project is not well supported.
I succeed to manage fews components with the testID props which is supported by xcode. But nor for all of them on my RN project.

I think, it’s more a question for react-native to better manage testID and UI Tests on xcode, than fastlane to adapt himself.

Источник

React Native: snapshot/screengrab support #13859

(Issue opened by request from fastlane/docs#626)

New Issue Checklist

• Updated fastlane to the latest version
• I read the Contribution Guidelines
• I read docs.fastlane.tools
• I searched for existing GitHub issues

Issue Description — (Only tested Screenshot (iOS), not Screengrab (Android))

Setting up RN build/release lanes with existing guides works fine out of the box! 🙂 (standard guides)

Having huge issues with screenshot, which was the entire reason for looking at fastlane to begin with.
Would love it if there were to be a how-to on supporting this, without introducing invisible hacks that depends on libraries like redux and therefore also react navigation with redux (which seems to be a deprecated feature). Or removing accessible features within the app.

As stated elsewhere, i added the prop testID=» » to the elements, especially those where which i would interact with. I also tried decorating it with accessible= .

Sometimes it says «Timestamped event matching error failed to find matching element», other times it seems to capture an element, but instead of refering to the element by the testID, it seems to create its own identifier which just contains all the text.

I think this is more of a recording issue, but since it was asked to be created as an issue here by one of the contributors, i did so.

Workaround

Its mentioned elsewhere to create a nearly invisible «button» which gets tapped, and updates the redux navigation state. By doing so, you can just refer to the same element, and tap it on each screen to go to the appropriate screen afterwards.

This might work for redux users, but not all apps use redux. And i dont believe that adding the «complexity» of redux to the app, for the benefit of trying to use this feature.

React-Navigation will also stop supporting this behavior in the next version of React-Navigation:
https://reactnavigation.org/docs/en/redux-integration.html

Workaround 2 (Have not managed to get this to work myself — but suggested somewhere)

Set accessible= on elements which gives you a hard time.
Applications are actually required to be accessible in Norway (and from 1.1.2019 — The entire EU).
Hacking the app, and thereby making it less accessible is therefore not a wanted operation. Neither is making this change back and forth everytime a new screenshot is to be taken.

I can see that i would be a well invested effort in the later game of any application (adding and removing accessibilty for the sake of the screenshots) — But in the early stages of the app, screenshots might rapidly change — and therefore it would be very time consuming if we were to do this «dance» everytime.

Reason for using screenshot:

Localization of app and framing w/ localized text.

Environment

Issue is not directly related to anything fastlane, as i dont get far enough in the setup.

The text was updated successfully, but these errors were encountered:

Источник

React Native: snapshot/screengrab support #13859

(Issue opened by request from fastlane/docs#626)

New Issue Checklist

• Updated fastlane to the latest version
• I read the Contribution Guidelines
• I read docs.fastlane.tools
• I searched for existing GitHub issues

Issue Description — (Only tested Screenshot (iOS), not Screengrab (Android))

Setting up RN build/release lanes with existing guides works fine out of the box! 🙂 (standard guides)

Having huge issues with screenshot, which was the entire reason for looking at fastlane to begin with.
Would love it if there were to be a how-to on supporting this, without introducing invisible hacks that depends on libraries like redux and therefore also react navigation with redux (which seems to be a deprecated feature). Or removing accessible features within the app.

As stated elsewhere, i added the prop testID=» » to the elements, especially those where which i would interact with. I also tried decorating it with accessible= .

Sometimes it says «Timestamped event matching error failed to find matching element», other times it seems to capture an element, but instead of refering to the element by the testID, it seems to create its own identifier which just contains all the text.

I think this is more of a recording issue, but since it was asked to be created as an issue here by one of the contributors, i did so.

Workaround

Its mentioned elsewhere to create a nearly invisible «button» which gets tapped, and updates the redux navigation state. By doing so, you can just refer to the same element, and tap it on each screen to go to the appropriate screen afterwards.

This might work for redux users, but not all apps use redux. And i dont believe that adding the «complexity» of redux to the app, for the benefit of trying to use this feature.

React-Navigation will also stop supporting this behavior in the next version of React-Navigation:
https://reactnavigation.org/docs/en/redux-integration.html

Workaround 2 (Have not managed to get this to work myself — but suggested somewhere)

Set accessible= on elements which gives you a hard time.
Applications are actually required to be accessible in Norway (and from 1.1.2019 — The entire EU).
Hacking the app, and thereby making it less accessible is therefore not a wanted operation. Neither is making this change back and forth everytime a new screenshot is to be taken.

I can see that i would be a well invested effort in the later game of any application (adding and removing accessibilty for the sake of the screenshots) — But in the early stages of the app, screenshots might rapidly change — and therefore it would be very time consuming if we were to do this «dance» everytime.

Reason for using screenshot:

Localization of app and framing w/ localized text.

Environment

Issue is not directly related to anything fastlane, as i dont get far enough in the setup.

The text was updated successfully, but these errors were encountered:

Источник

WWDC 2016 Labs Highlights

Most of my time in WWDC was spent in the labs — since sessions can be downloaded and watched later. I’ve learned A LOT and I would love to share of this knowledge with you.

Notice — this post will not cover any of the new iOS 10 features or anything from the sessions I did go to. Watch them for yourself!
This post will cover only what I have learned in the labs.

Xcode Open Hours

SourceKit crashes

We have a lot of SourceKit crashes. This causes us to lose autocompletion, colors, cmd+click etc… We don’t know why and it’s annoying as hell.

I tried to understand if there’s a way we can see the crash logs.

Fortunately for us — there is.
Unfortunately for us — it sucks.
But — we’ll take what we can get…

We can’t see logs for crashes that already happened — but we can initiate a debugging session and hope that SourceKit will crash during that session. And let’s face it… It probably will…

Open Terminal and enter the following:

Replace # with the following values:
1 — For requests only
2 — For requests + responses
3 — For requests + responses + notifications

This will allow you to see all of the messages between Xcode and SourceKit. Once SourceKit will crash you should be able to see the line that caused the actual crash and hopefully will provide enough clues to how to deal with it.

External Frameworks

I initially wanted to ask about how to turn some code I’m working on into a framework we import to various apps we build. The requirements were to be able to use it on the same project as a different app (for the ease of changes) but still treat it as a separate framework. I was having some issues doing that myself.

Good thing I did that because turns out we were “doing it wrong” with another framework we were using. Our project was using a Workspace in order to include another framework’s project and add it as dependancy.
Turns out this is a workaround and not how it should be done

Leaving it this way could cause a few problems in the future (the Apple engineer claimed he could think of at least 15 potential issues) plus the chance of being rejected from the app store in some cases (yes — I found it hard to believe as well…).

Here’s the correct way to do it:

1. Open your app’s project
2. Drag the framework project into the app’s project
3. Add the framework as Target Dependency — in the Build Phases tab
4. Add the framework as Embedded Binary — in the General tab (choose from the product folder)
5. Add the framework folder to the Frameworks Search Paths — in the Build Settings tab

At this point my project wouldn’t compile anymore.

I added a couple more steps which fixed everything and allowed me to use the framework in the same project without using a Workspace — the way “it should” be done:

6. Tap on the app’s in the project hierarchy and then File->Project Settings

7. Tap on Advanced and change it from Legacy to Xcode Default

You can now remove the existing build folders from the project and Xcode should continue as usual.

Swift Open Hours

Optional Booleans

I was having some issues with reading optional Bool values from Swift to Objective-C. Turns out there is no representation of a Swift optional Bool variable in Objective-C. Unlike optional NSString and NSNumber — which can be nil in Objective-C — Boolean values cannot be nil in Objective-C.
Changing to Bool to a non-optional variable solved the problem.

On Demand Resources Lab

Third party libraries

I already knew the answer — but I felt like I had to ask.
Can we use the On Demand Resources capability in order to lazy load third party libraries like Card.IO?

The answer was, obviously, “NO” — but they were interested in this use case.
They suggested we submit a feature request and it might get things moving. The more duplications in requests the better by the way..

UI Testing And Continuous Integration

Correct workflow when using the record feature

Unfortunately, the record feature is far from perfect. It gives you a nice place to start but there’s a few hours of refactoring after you complete recording a test.

I wanted to make sure I’m not doing anything wrong — and turns out I wasn’t — this is how it works.

A good practice will be to start creating known working test “actions” like “login”, “go to specific screen”, “enter text into search bar”, etc…
Then — we will only need to record very small parts of the test instead of entire flows.

Accessibility labels

We kind of suck with accessibility labels.

A lot of actions I recorded were searching for static text in order to find the UI controls instead of the preferable way — which is accessibility labels.
Adding more accessibility labels through the app will allow for easier and quicker tests creation + the added value of actually having accessibility labels for the hearing impaired.

Reseting the app states after (before) tests

When running a UI tests suit you would probably want to run a few tests that doesn’t rely on each other. Each test should start with a clean app.

That’s why I used to add “delete accounts and logout” actions to the end of tests. The problem is when one test fails in the middle — it also fails to remove the accounts and logout. So following tests will start with the changes that were made by the failing test.

I asked if there’s a way to reset the app state each time a new test starts. There’s no way to do that — but Apple engineer suggested to add a testing flag in the project settings that will be detected by the app (when loading) and will cause it remove all user data when that flag is active (via code).

Timestamped Event Matching Error: Failed to find matching element

When recording a test, selecting an already selected UITableViewCell will cause the test recording to crash with the message “Timestamped Event Matching Error: Failed to find matching element”.

Turns out Apple has an open bug with this exact issue but didn’t know the reproducing steps. So we were both very excited I know exactly how to crash the recording every time.

I still need to create a new project and see if it happens there as well — or is it specifically on my app. I really hope I would be able to help them fix the problem soon.

Источник