Craig Harry
-
Posts
6 -
Joined
-
Last visited
Content Type
Profiles
Events
Forums
Blogs
Gallery
Downloads
Posts posted by Craig Harry
-
-
On 11/7/2020 at 6:22 AM, PinkElephant said:
For me this is a bug in the user interface of this function, hopefully solved with a future release.
I wouldn't bank on it
-
When.are.the.non-existent.offline.notebook.sync.issues.going.to.be.fixed??? Can we get an update even? This is SOOOO frustrating, neither my iPhone or iPad will download a notebook for offline use. Ridiculous. I will cancel my subscription if this isn't fixed soon because you're taking my money and only making your software worse with each update.
I honestly can't believe that your CEO has the balls to film these marketing videos, and send out these marketing emails, when you well know that your new iOS upgrade is complete trash. Fix it already, and stop with the marketing until your product actually works.
- 1
-
@ShaneD tried your workaround on iPad (turning off screen auto-lock), and then began moving about 75 offline notebooks one by one to not be offline. On at least half, if not more, when moving the slider to "offline off" it reverts back to being online. I move slider to off, press "Clear", and the notebook slider automatically moves back to the right. This is true in just about every case where the forever-long download is in some form of progress.
Do you have any idea when this issue will be resolved? It's made the iOS versions of Evernote, which people are paying for, completely useless for close to two months now.
- 1
App Performance Issues: Slowness/Poor Responsiveness/Lag
in Evernote for iOS Issues (Versions 10.0 and above)
Posted
NO! This is not a workaround. Why are you even proposing this nonsense? The iOS app needs to be fixed, because Premium users are paying $70/year for an app that works. This one doesn't, but used to. So we're paying for the app to go backwards, not improve.
And in case you don't have an iPad or never used one, most of them only operate off WiFi and do not have a cellular phone connection. Therefore your "workaround" will not work.
The workaround is to FIX.THE.APP.