This is not a permanent fix but a bypass until resolved, rolling back to python 3.11.X resolved the issue. Seems to be compatibility issue between DAP 1.1 and python 3.12.x

this version is riddled with issues

Installed new dap tool on new VM Old VM could run dap syncdb --table accounts no problemsnew dap tool with dap_api_url set to https://api-gateway.instructure.comdap_client_id matching old VM, dap_clie...

Can we add a feature to fully load the entire database with all existing tables in their related schemas for when an organization has to load a new database? 

i fought insanely hard for like 4 hours on this topic Friday, the whole update AWS thing isn't even relevant as it has nothing to do with local certificates, just lucky for those that worked on. W...

Can we add a feature to fully load the entire database with all existing tables in their related schemas for when an organization has to load a new database? 

i fought insanely hard for like 4 hours on this topic Friday, the whole update AWS thing isn't even relevant as it has nothing to do with local certificates, just lucky for those that worked on. W...

this is not a solution

I was able to resolve my issue by uninstalling python 3.12 and installing python 3.11, hope this works for you!

This is not a permanent fix but a bypass until resolved, rolling back to python 3.11.X resolved the issue. Seems to be compatibility issue between DAP 1.1 and python 3.12.x