Unable to rename App

get an error "TypeError: cannot read properties of undefined (reading'message') when trying to rename an app.

any thoughts ?

1 Like

this is on 3.39.0-edge

Hi @alucero,

I was unable to reproduce this on my end. Are you still having issues?

Yes. I'm waiting for your next stable release to try that and see if that fixes it.
I'm unsure if I can change versions from 3.39.0-edge to 3.33-stable.

thanks

Hey @alucero,

Just checking in again to see if this is still an issue?

yes, still an issue, but we are still on the same version.

Thanks! Looking into this now.

What type of browser are you using? Are you able to rename an app when it's open in edit mode?
image

upgraded to 3.52.1 and the issue still persists. sigh

same error when in edit Mode. I'm using Chrome 125.0.6422

Hey @alucero,
Hope you had a good weekend. Would you mind providing some more information that should help our team troubleshoot:

  • Is this happening with all of your apps?
    • If not, can you share an export for me to test?
  • Can you save other changes to the app?
    • Does the issue happen for everyone in the org?
  • Are there any errors in container logs?
  • What plan are you on?
    • If self hosted, do you have access to source control?

Thank you for your patience!

  1. yes , happens with other apps cannot rename
  2. yes we can save changes, yes happens to everyone in the org
  3. no errors in the logs
  4. self hosted.

on a related note, we cannot save changes to db resources either.

1 Like

Thanks for getting back to me so quickly! Just followed up with our dev team.

That is good to know. The two issues may be linked.

Hmm, we haven't ran into this issue before so we may need to gather more information to get a better grasp of the problem. Apologies in advance for the barrage of questions.

  • Please grab the requestId from the failing request in the Networking tab of your developer tools and then share all container logs from all Retool services that have that requestId UUID.
  • If known, what version did this start on?
  • Would you mind sending over a video of the editing resources bug?
  • It looks like your encryption key is missing. Has this been resolved?

To get that request-id:

  1. Inspect the page
  2. Click Network
  3. Click the clear button on the upper left hand side
  4. Make the request to edit
  5. Click the request
  6. Copy the X-Request-Id
  7. Screenshot the Response tab

I couldn't click to rename in Chrome with web developers tools, so I tried it in Firefox.

I was tailing the logs for retool-onpremise_api_1 , i didn't see a request.

here are FF response headers:

Connection: Keep-Alive
Date: Thu, 27 Jun 2024 16:49:24 GMT
Keep-Alive: timeout=5, max=100
Server: Apache
Strict-Transport-Security: max-age=63072000; includeSubDomains; preload
Vary: Accept-Encoding
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
content-length: 72
content-type: application/json; charset=utf-8
etag: W/"48-s/4uL9Tc8t+RnmYAFWZkEncx5yI"

Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,/;q=0.8
Accept-Encoding: gzip, deflate, br, zstd
Accept-Language: en-US,en;q=0.5
Connection: keep-alive
Content-Length: 60
Content-Type: application/json
Host: retool.jelli.net
Origin: null
Priority: u=1
Sec-Fetch-Dest: document
Sec-Fetch-Mode: navigate
Sec-Fetch-Site: cross-site
Upgrade-Insecure-Requests: 1
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:127.0) Gecko/20100101 Firefox/127.0

response
{"success":false,"message":"Authentication failure. Missing xsrf token"}

we started seeing this issue on 3.39.0-edge
video

encryption key issue resolved

@alucero @mikec,

Could you please navigate to Settings > Permission Groups and Settings > Users and send a screenshot to show the permission group. As well as a screenshot showing View, Edit, Own permissions on the impacted Apps, Workflows, Resources.

Some additional questions:

  • Do you have SSO configured?
  • Are you employing Spaces?

Thank you for providing all this detail!

no SSO
not using spaces



Hi @alucero

Just wanted to let you know we're still working on this and I will comment with any updates as they come.

thanks, we were able to make the change directly in the db. for now we are unblocked.

1 Like