Error 400 on Sync: Fully updated Adobe AI & CC Mapping Extension

[ChrisMyers_NewQuest]

Hello, 

We are receiving  Error 400: Failed when attempting to sync. 

Mode: Legacy mode (for Esri VectorStreetMap use)

Illustrator version: 26.3.1

CC Mapping Extension Version: 3.2.0

 

Thanks, 

Chris

[ChrisMyers_NewQuest]

Interestingly, we have a user with AI v26.3.1 and CC mapping extension v3.1.1 (unupdated) and she is able to sync. Is there a way to revert versions of the mapping extension? Ideally everything works with the tools being fully updated, but we need to figure out how to get the extension working for day to day workflows. 

Thanks again, 

Chris

[Xingdong_Zhang]

@ChrisMyers_NewQuest Sorry for the inconvenience. The team has been able to narrow down the problem and is currently working on a solution. 

[ChrisMyers_NewQuest]

Thank you! 

[Xingdong_Zhang · Accepted solution]

@ChrisMyers_NewQuest 

Thank you for your patience. The team have worked hard and resolved the 400 sync error with the legacy mapping profile. Please try your workflow again. We are sorry for the inconvenience caused by this issue. Thank you for using Maps for Adobe for your design work,

Xingdong

Maps for Adobe Team

[MaxWard]

Hello!

We are having the same issue (Error 400: Failure). We are using AI v28.5 and the Arcgis CC v3.7 I am on a Mac Sonoma 14.5 and my colleague came across the same error on her PC (not sure what version). 

I spoke with support and it sounds like this issue may be on the backend. Do you know when this is anticipated on being resolved?

Thank you, 

Chris 

[chadherschberger]

Hello,

Also having this issue with most vector assets. in addition to "Failed" getting Error 400: java.lang.Exception: Could not service request. most recently attemping to sync the VectorStreetMap asset for the DC area. Using most recent extension on the more recent Photoshop (rosetta) and Illustrator (Sillicon) 

[Xingdong_Zhang]

@chadherschberger Sorry for the inconvenience. A similar issue has been reported and logged BUG-000151284. The team is investigating the cause of the problem and is working on a solution. Meanwhile, instead of adding it as a layer, you may want to try using VectorStreetMap as basemap from the basemap gallery in the compilation window.

Please let us know if the workaround doesn't apply to your workflow

Maps for Adobe Team