[Waiting for user confirmation] Custom post type archive page not displaying properly with WPML

Background of the issue:
Hello, this is in follow up to https://wpml.org/forums/topic/custom-post-type-archive-template-breaks-on-translation-url/

I was not able to respond to that thread directly since it had been closed. I had notified the agent I would be away but I guess that was missed in the communication. Apologies for needing to create a new thread about the same topic.

In the last reply, it was pointed out that the *single post* on the *translated* custom post type *archive* shows correctly if no Punjabi characters (unicode characters) are used in its slug. In other words, the "critical error" message of the single post on the archive page goes away when no Punjabi characters are used in the post's slug. This applies to the post listing itself in the query loop, not the design of the entire custom post type archive *template*, which remains broken. Screenshots in the other thread of this topic explain what is meant by this.

However, now we know that if the Punjabi translations of *all* the individual posts use English characters in their slugs, then the custom post type archive page appears correctly. If one of the posts uses Punjabi characters in its slug, then the translated *custom post type archive page* breaks.

However, I feel this does not explain everything because the translations of other posts appear correctly when using Punjabi characters in their slugs. E.g. hidden link

Can someone please help to explain why it is only the custom post type posts that can not use Punjabi characters in their slugs, to avoid this issue? And, why do Punjabi characters in the single post slugs cause the *custom post type archive page* to break, but not the single posts themselves?

The 'break' only happens on the custom post type archive page when any of the single posts of that custom post type use Punjabi characters. All other pages of the entire site appear correctly when using Punjabi characters in the slugs (i.e. for pages and posts).

Also, this issue does not happen on category archives of native WordPress posts when the posts use Punjabi characters in their slugs hidden link

Could our issue be related to the known issue described here: https://wpml.org/forums/topic/archive-custom-slug-translation/ ?

We purposely did not add a translation under WPML > Settings > Post Types Translation > "Set different slugs in different languages for [custom post type name]" because we read that it a known issue with WPML that if we do set a translation in this field, it will cause a break. (See screenshot). We were not made aware that the *single posts* also could not not use translations.

Given that it is a known WPML issue to not be able to translate custom post type slugs at the moment, and all other slugs of native posts can use Punjabi unicode characters, can you confirm that unicode characters in custom post type single post slugs is definitely not a WPML issue?

Although its not completely understood, would this documentation be a solution for us? https://wpml.org/errata/incorrect-links-for-custom-post-types-and-taxonomies-sharing-the-same-slug/

Thank you very much for your help.

Symptoms:

Questions: