question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

React Native .from().select() promise never resolves in release (Expo)

See original GitHub issue

Bug report

Describe the bug

When testing the from().select() function in debug mode in an ejected Expo app the data is returned successfully, however, once you switch to the release variant, nothing is returned. The app does not crash meaning no major errors are being thrown.

To Reproduce

const { data, error } = await supabase
      .from('table')
      .select('*')
      .eq('column', variableToMatch);

Expected behavior

The expected behaviour is that the call will return the requested data from the Supabase table or an error suggesting that something went wrong.

System information

  • OS: macOS
  • Version of supabase-js: v1.11.12
  • Version of Node.js: v14.16.0
  • Version of Async Storage: v1.15.4
  • Version of Expo: v41.0.0
  • Version of React Native: v0.63.4

Additional context

I have been getting these logs: Error getting session from URL., nw_socket_handle_socket_event [C5:1] Socket SO_ERROR [61: Connection refused], nw_connection_get_connected_socket [C5] Client called nw_connection_get_connected_socket on unconnected nw_connection, TCP Conn 0x2806304d0 Failed : error 0:61 [61], SocketRocket: In debug mode. Allowing connection to any root cert but I am uncertain whether the last four pertain to Supabase. Happens on both Android and iOS.

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:33 (10 by maintainers)

github_iconTop GitHub Comments

2reactions
He1nr1chKcommented, Jun 13, 2021

@kiwicopple honestly have no idea, never really looked into how (or why) react-native-url-polyfill works.

2reactions
He1nr1chKcommented, Jun 9, 2021

After many wasted hours @Hannes1 figured out that react-native-url-polyfill was the culprit. We were using the latest version but when we downgraded to v1.2.0 the promises were getting resolved. Thanks @soedirgo and @kiwicopple for the help. Love your product btw, plan on using it for my personal projects into the foreseeable future.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Why is promise from fetch not resolving (react) - Stack Overflow
I am new to promises and async/await in react. I have been reading but still, I don't understand why the promise from my...
Read more >
MediaLibrary - Expo Documentation
Are you using this library in a bare React Native app? ... Promise<boolean>. Returns a promise which fulfils with true if the album...
Read more >
Troubleshooting - React Native
These are some common issues you may run into while setting up React Native. If you encounter something that is not listed here,...
Read more >
Invalid Hook Call Warning - React
You might be using a version of react-dom (< 16.8.0) or react-native (< 0.59) ... You can only call Hooks while React is...
Read more >
React Native i18n with Expo and i18next - Part 1 | Phrase
return new Promise((resolve, reject) => { ... Similar to React Native's Platform.select(),. * i18n.select() takes a map with two keys, 'rtl'.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found