You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There seems to be a bug sometimes creating a second app connection after the first was successfully setup (and received an event). It looks like a bug with the old app pubkey being cached somewhere, causing an instant navigation on the /created page.
video.mov
A temporary workaround is to do a hard refresh before creating a new app connection
The text was updated successfully, but these errors were encountered:
SQLITE cascading delete is not working, so when deleting an app and creating a new one, old request events are linked to the new app.
I realized to do this properly we should also delete the response events, which currently have an issue with the constraint to payments, which is solved by #226
Update: cascading delete is working initially, but seems like a bug with re-using IDs. This should be solved if we add AUTOINCREMENT to all our primary keys.
There seems to be a bug sometimes creating a second app connection after the first was successfully setup (and received an event). It looks like a bug with the old app pubkey being cached somewhere, causing an instant navigation on the
/created
page.video.mov
A temporary workaround is to do a hard refresh before creating a new app connection
The text was updated successfully, but these errors were encountered: