Long MXI filename and Bundle ID dilemma

The bug has been fixed. It used to be rejected even if they are matched. Thanks to you, @Akshay A  and to the engineering team.

The manifest file name and the bundle ID do not match. Please ensure that they are the same, and you will then be able to upload the ZXP file.

@Akshay A : I have resent the email with the subject title that is similar to this thread's title. The zxp file was not attached but sent in the email text as a Google Drive link.

Hi @Pixelsplasher, I noticed that you have attached the zxp file directly to the email. However, please note that Adobe policy prevents these types of emails from being delivered, and as a result, I am unable to download the zxp file. I request that you upload the file to a preferred cloud sharing website and share the link with me so that I can download it.

Thank you for your cooperation.

I have sent the zxp file, @Akshay A 

Hi @piXelsplasher, Kindly share it with the review team at ccintrev@adobe.com. To do so, please upload the file to a cloud-sharing website and send us the link via email. This will enable our engineering team to identify and address issues with the zxp file.

Thank you for your cooperation.

Thank you for your reply, @Mayanka Sharma . I am still seeing the same error.

Thanks for tagging me @piXelsplasher . Are you still seeing the same error? 

@Akshay Abrol Can you please create a support for DD/Exchange and share with the team?

@Mayanka Sharma 

Reuploading the latest version without editing the manifest already returns the unknown error since the mxi filename must be the same and should match the bundle id.

After doing these steps:

• update the downloaded manifest by adding the host app details

• bump the version to the desired one
  

My dilemma is the same. I think the mxi filename length restriction was placed just recently. Any chance to have it repealed until we have the ability to shorten the bundle ID?