I’m really worried, maybe something serious to the developers …
shame because in my opinion, it is the best writing software for ipad.
what a pity
Agreed. I’m sure they are overwhelmed by the dire consequences of the premature release of the “new” file format support. I’m sure they’re devoting all their time toward a resolution, BUT ignoring the customer could be perceived as indifference.
I’ve asked for update on why we haven’t received info on what they plan on doing to fix this. They’ve gone MIA. No response. I feel they’ve abandon ship.
Sorry for providing support on the forum slowly on these days. We’re regret about recent issues with iCloud. Let me give you an overview of these issues so you have a better understanding what is going on.
Regarding some recent issues, they are related to iCloud and our data migration tool. Some months ago, our team realized our old resource file format wasn’t working well with iOS Storage Optimization (when enabled iCloud Drive) and the system would evict your files from local to iCloud server when the device is in low storage or under some circumstances (Apple doesn’t tell the transparent process how this logic works). When some of our resource files were evicted to the cloud server, the app couldn’t render notebook content on the page properly. Thus, we decided to move to new file format.
This required the data migration to take in place. However, iCloud occasionally got stuck during the data migration for many users and that caused the notebooks couldn’t be transfered to new file format properly. As a result, instead of showing your actual notebooks, some of those items are now shown as resource folder with .xml, .js, html, etc… Even worse, your files/folders are being duplicated multiple times. After scanning through our code, we eventually found out the data duplication was not coming from our data migration code entirely, but it was partly with iCloud service itself when it came to manipulate a lot of resource files in a short time.
There are times iCloud couldn’t “see” the files already saved on local storage and the other time the app couldn’t fetch the file existence state on iCloud server, thus it would create extra copies of a notebook. This leads to #1 and make the app running slowly and it could cause crashes when iOS run out of system resource. Unfortunately, for such events, the app couldn’t detect and remove extra copies automatically. Instead, please try to clean up your library manually in these steps: On your iPad, return to home screen, open Files.app, go to iCloud Drive > Notes Plus > find the extra copies (in .npn format), now tap “Select” button at the upper right corner, select the items, tap “Delete”. In case you delete a wrong item, you can go to “Recently Deleted” section in Files.app at the left sidebar, restore the deleted items.
After the migration process has been completed, the data duplication issue should not happen anymore.
When we supported users with the iCloud-related issues, some users confirmed they could get back to normal state after turned off iCloud and re-link with iCloud sync (remember to choose “Not to keep the data on the device” when asked so your data won’t be duplicated if you enabled iCloud syncing again).
Since there are many users encountered different migration results, we couldn’t give support to your specific cases on this single thread. Kindly redirect your specific issues with some contexts (which cloud service/what is the symptom, etc…), the more details you provide the easier we could help you. Our support email is: email@example.com
We’re committed to fix whatever left from our releases to bring back stability. Our Dev Team is still fixing bugs from our end and work on iPadOS bug fixes.