Changing the name of the target project, changing it back, then migrating the DPS content actually worked! Well done, Christophe! I wouldn’t have come up with this solution myself.

That’s not it—I’m signed in to the DPS page as well.

Resurrecting this thread for the recurring error. I can’t seem to migrate at all now.

I don’t think it was the degradation—it failed again this morning. But—after unchecking the “Force overwrite already migrated articles” checkbox, everything migrated OK. There are likely minor variations somewhere between the new articles, revised articles and untouched content that got things confu...

Attempts to migrate a “classic” DPS folio fail with the error, “Folio “folio name”; there was a problem communicating with the server, the operation failed after “5" retries."

My limited test says "no," because preview apps must be signed with the developer profile, and iTunes Connect requires apps to be signed with the production/distribution profile.The followup question is how to get a preview app into the hands of testers or content reviewers. Send them the properly s...

I ran into this yesterday also. Today all seems to be working. Go figure.

Thanks Neil.We are, and I will.* The card really is applied--I can edit everything except the type and have the change show up.*First I'm going to remove the article with the HTMLResources and see what happens.

Also thought I'd addd that this problem is unique to this project. A second one, also built with the Folio Migration tool but without any HTMLResources, works correctly.

Tried that. No joy.One thing I forgot to mention that may be important, or not, is that the content was brought over via the Folio Migration Tool, and does include a HTMLResources file. But I'm not using any specified font as you can see, and I didn't upload any font assets when I built the app.