Fragments still getting (attempted) annotations

[jarredt]

I am seeing warnings on both the native and web versions of our app that Fragment elements are being given dataElement props. I have tried without specifying any "annotate-fragments" setting, setting it to false, and setting it to true, but I get the warning no matter what.

[rcmaples]

Hi there @jarredt, RC here with FullStory's support engineering team. We're not set up to troubleshoot issues via Github issues currently. If you're still running into issues here can you reach out to mobile-support@fullstory.com? We'll be more than happy to help out.

Thanks so much!

[shaunp-street]

For anyone googling around trying to find a solution to this, add the following

[ '@fullstory/babel-plugin-annotate-react', { native: true, ignoreComponents: ['React.Fragment'] }, ],

[cansin]

I am doing exactly what @shaunp-street suggested, but to no avail. Still getting Warning: Invalid prop fsTagNamesupplied toReact.Fragment. React.Fragment can only have keyandchildren props. warnings. Anybody with a solution?

[RyanCommits]

@cansin Could you share the source code for how you're using React.Fragment? If you have multiple uses of React.Fragment and not sure which one is causing this error, I suggest narrowing it down to a specific example.

[broshkabro]

Seeing the same issue for React app. Adding

• [ '@fullstory/babel-plugin-annotate-react', { ignoreComponents: ['React.Fragment'] }, ],
  or
• ["@fullstory/babel-plugin-annotate-react", { "exclude": ["Fragment"] }]

does not help. Could this be because of <></> usage (not React.Fragment)?

[RyanCommits]

@broshkabro I'd be happy to look at this - Could you replicate this issue in a sample project?