Aakash K Balaji
Aakash K Balaji
^ Occuring on Mac for me currently
Looks like for me it was caused by the following setup ``` Amplify.configure(amplifyconfig); //Uncommenting this code causes issue // const existingConfig = Amplify.getConfig(); // Amplify.configure({ // ...existingConfig, // API: {...
Still facing this issue on Mac. Even stopping/restarting supabase does not pickup new function changes. @Bijig0 did you ever solve for mac?
I'm still having syntax issues like `db.collection` vs `collection(...)` due to firebase versions. Any updates on when we can expect this package to match latest firebase sdk?
Is there currently any place the view the logs? I am not able to find on docs. Edit: all logs available on cloudwatch. But would definitely love logs streamed to...
Further findings: - Removed `lastMessage` property, issue still persists so ruling it out as issue - When I pull conversation messages in front end via selectionSet, this issue does not...
Updated lambda code to pull messages via `selectionSet` as opposed to using `conversation.messages()` function to make a new request, fixed the issue, messages are all pulled as expected. Still keeping...
@david-mcafee I returned the `message` but can confirm it works without, because when I refresh the page, it pulls the latest conversation, and all the messages are present. I logged...
Actually seems to be a larger issue of getting a similar error when trying to `get` any non-existent item from: ``` { "errorType": "TypeError", "errorMessage": "Cannot read properties of null...
Any update on this?