Nick McMillan

Weighing in here, the crash is occurring for me on `"react-native-track-player": "2.1.1"`. This is a screengrab from Crashlytics. Same error message as OP.

Is this PR related? https://github.com/DoubleSymmetry/react-native-track-player/pull/1167 It might be better to ignore errors silently than to crash for real users.

Possibly related; I'd like to offer the user the option to enable/disable haptics. But I'd only like to show this toggle in the UI if their device actually supports haptics....

I'd love to see this issue resolved. In the meantime this is how I'm getting around it with StaticQuery, as suggested by @greatwitenorth above. ``` import React from 'react' import...

I had to ask the content editors to avoid using non-ASCII because of this same issue. It would be great if there was an actual fix...

It's been about 2 years since I've touched this project so haven't tried to run it locally for a long time. Was it not running locally for you? I presume...

Same situation here. Small (10-ish SSR pages) NextJS site. No idea what's happening during these ~8 minutes. ``` 2021-12-03T04:05:18.299Z [INFO]: Starting SSR Build... 2021-12-03T04:13:09.007Z [INFO]: SSR Build Complete. ```

I think that's fine if all that's needed is a static site - which is what `next export` generates. But if we want a site with any SSR pages -...

[justyn-clark](https://github.com/justyn-clark) The problem this thread is discussing relates to Amplify's slow SSR build system, the bottleneck has nothing to do with using NextJS, even less to do with Gatsby.

I'm finding this predominantly occurs when tapping on the Icon.