could you add a debug log, seems there goes something wrong with setting the cors headers.
yes, i will remove the service and re-initialise with logging
On observation:
when adding a couch database the database is added then afterwards a the message regarding adding cors appears. There can be a delay between the message stating the service is created and the setting CORS message.
Perhaps, if thinking the service is completed, the user then goes ahead with creating the table and user not realising the cors settings are incomplete, this leads to the cors addition failing.
Just an idea from observation
O will recreate with login and send details to you and if possible video the cors issue i highlight above
Deleted service and readded it, log attached
wappler.zip (9.5 KB)
CORS incorrectly set at end of process
1 Like
found the issue - it seems a racing condition, the couchdb service was not fully running when we try to setup the cors - so that is why it didn’t went well.
will improve that and add more solid reporting
2 Likes
hadn’t noticed this before but in case it is related, long delay
cors-spinner
This has been fixed in Wappler 6 Beta 2.
This topic was automatically closed after 30 hours. New replies are no longer allowed.