The reason here was, that the changelog mentioned some potential 3rdparty integration testing, so we waited for a bit to give those time to catch up ideally. Given your reminder I now pushed the update though as anyways 2 weeks passed.

Apparently there was a typo or missing quotes in the env.sh maybe @shivamkb17 could share those details for others.

@girish Amazing! Updating now. Thank you!

Nevermind -- looks like just a stale session. New one worked fine!

@girish Is there an estimated timeline for 7.5's release? I'm waiting for an upstream fix in 2.18.0 of chatwoot and it sounds like that's blocked on the cloudron update then?

Also, the app logs will help.

@girish Hi i recieved today's email which you sent i am reverting back to 1.17.1 thank you.

I commented on the github issue, as I am not sure how an asset rebuilding would solve this. But I lack deep insight into the app as well.

@nebulon Yes seems to work. Thanks for the speedy implementation!

Its updated already.

@girish thanks, that seemed to work now! Hope I find time to set up the rest of it soon

Thank you very much, it worked!

@sufian-mughal Do you know where livechat@xyz.com is coming from? Maybe you set this somewhere inside the app?

@sufian-mughal Let's follow up at https://forum.cloudron.io/topic/8828/chatwoot-unable-to-send-chat-transcript

It is out now, app is updated.

Update: This big has been fixed in one of the latest updates.

The latest package supports alias domains. See https://docs.cloudron.io/apps/chatwoot/#custom-helpdesk-domain

There is a new patch release coming up, so maybe that brings in some fixes.

@luckow not sure I like the sound of 'surprise' but could be good !