PinkElephant

In the meantime I had contact with support. They told me the issue is known and EN is working on a solution. Since I do not have the issue, maybe anybody here who has the problem may contact support as well and help them with activity protocols or other information if requested.

Here is a description about issuing a support ticket on account issues. If you are basically locked out, I think this should apply to your case:

The keynote is on the 10th of September, the official release of iOS 13 and iPadOS will be shortly after. I assume that any EN release thereafter will be „13-enabled“. At least I hope so. The same with MacOS „Catalina“ !

I can confirm this on my iPad Pro 10.5 on iOS 12.4 (soon going to 12.4.1, just need to find a hotspot). It did not cross my view before because I usually do not present out of EN. Do you intend to place a support ticket ?

The nesting of tags IMHO is good for keeping the tags organized, not for the tagging itself. Currently I take some time every few month or so to review the use of tags, unify those who are synonyms, exchange and delete those that do not get much use (and probably will not get for the near future) etc. Here nesting gives a structure for a quick overview over the 3-digit number of tags I have created up to now. The use of the tags is independent from nesting. I can tag without problems in the Webclipper or the iOS client as well, where the nesting will not show. What is a bigger problem (but for both notebook assignment and tags) on the mobile platform is that one can work on a single note only at any time. So for EN housekeeping it is better to use a desktop client, where several notes can be organized at once.

In addition, you can share an open Link that can be accessed using a browser without having Evernote. And you can share via E-Mail. I use the share function as well to get links created in my task manager (Things 3). The task is controlled in Things (like recurring reminders etc.), and by a simple click on the sharing link I can always open the corresponding EN note with all the details. Very slick !

... and I still do not have the Problem. Just to make sure the question was posted: Anybody here on a beta ? Beta iOS, beta EN, beta whatever else app may be betaing (surprise, surprise - currently, all of them seem to do it). On my iDevices, there is only release level, current iOS, official release iOS EN app, and no other beta-stuff. The app is running perfectly well and without waiting periods (excluding those happening on a weak mobile connection or bad WiFi).

This is not a bug, but a differing behavior by the two clients for iOS and Android. A bug would mean that it is intended to highlight on Android as well, but it wouldn’t work. But it is not intended to work on Android, it simply is not implemented there. So it is not a Bug, it is a non-Feature. EN is well aware that the differences between the clients are annoying to customers that use multiple devices. The current top management made it a top priority to reduce these differences. I am fine with this, working with EN on Win10, MacOS and iOS, always remembering what to do best on which platform. Reduce hopefully does not mean go for the smallest common denominator - EN is still running inside of operating systems, and their abilities can limit the functions on one device compared to another. I would rather not like to give up highlighting on iOS just because Android does not allow for something similar.

Have not checked it recently, but when I did last, there were 2 methods available plus the fallback codes generated when activating 2FA. - For Basic users there was only Google Authenticator available. - For paying users they would as well send one-time-codes by message to a mobile phone. If there are Apps that successfully mimic Google Authenticator I do not know.

Now, maybe look at it from the EN side. You are volunteering as a pro bono customer today, consuming resources, but not paying. The only reason to allow this type of customer today is to generate more paying customers tomorrow. Some companies do it by forcing „up or out“ after a trial period. EN doesn’t - you can stay on in Basic as long as you please. So why are you complaining that support will not listen to you ? It is one of the services that consume real money for real people giving assistance, and (surprise) they offer it just for those customers who are paying. We paying bunch are not paying for support, we pay for a bundle of improvements of which support access is just one, and even not the most relevant. If you are in urgent need for support, you can go Premium for just one month. This is a super bundle, because it opens additional features for you even for all the stuff you put into the account when you were on Basic. Examples: All of a sudden the note history is available (for example for recovery of unintentionally deleted data), for all notes, not only the new ones. OCR is there, for all notes, fully searchable. And support will listen during a full month - for not much more than a Cup of Starbucks brew. So again: What are you complaining about ? You get what you have ordered, basic treat or all inclusive, but there is nothing as a free lunch in town. So set the Web client to classic, and go ahead. Or move on, to where the grass is greener, the birds singing your song, whatever.

Stacks were relatively simple: one notebook can belong to exactly one stack, and if you define „not assigned“ as „assigned to the no-stack-stack“ you always have a clear structure. It can not be nested, no stack in stacks allowed. This is a database-field within „what is“, not an entire structure to support multi-level-nesting. And even this meant a significant change when introduced. But this is not the point: IMHO a simple notebook structure plus the flexibility of tags is what best serves the need to organize the type of information EN is build for. To change this would mean to give up focus.

Again technically spoken, if the note-notebook structure would be changed from 1:n to n:m (in relational DB speak), there would be an additional table needed to keep the data for the new flexibility. To read this, all syncing and search routines would have to be altered, and probably most of the back end supporting the EN servers as well. All of them, and it would for sure cost search performance, because it would mean another link table needs to be read out in each search job. It would probably be easier to create a new SW with this features, than try to rebuild the existing one. P.S. Just a user, not EN staff ...

For me it is as well only a shot into the dark. I do not have any of the problem described on my MacBook Pro, and this is how far I can assist here. If nobody else joins in, probably the best next step would be to float a support ticket, and look where it will take you.

To put it simple: In EN each note belongs to exactly one notebook. It can not have no notebook, it can not have more than one. And the data structure reflects this relationship called 1:n technically. To change this would probably mean rebuilding EN from scratch. With tags, it is different, because each note can have multiple tags, each Tag can be used for multiple notes, and a tag can „belong“ to another tag. This is why on the user interface, one can nest tags (at the moment only on desktop clients), and why tags are much more flexible than notebooks in their use. Conclusion: If you want to use EN as your „second brain“, you have to organize your content based on this structure. If you work against it, you will never be happy with EN - so better move on to another program than start the 1000-and-1st discussion here that nesting of notes and notebooks would be needed. No, it is not needed, if EN is used as it is build. Once you set up things according to the abilities of EN, you will find this aproach to be much stronger and more flexible than any nesting of notes. In practically all „nested“ structures (like the ones created by the file system in most operating systems like Windows), you typically end up with incoherent structures and duplicate documents. Both can be avoided by 100% when following the EN filing logic. A starting point can be found here: https://help.evernote.com/hc/en-us/articles/209006097

If you want seamless font management on all platforms, this means a restriction in fonts. When I wanted to have Calibri on my Mac, I had to „steal“ it from my Win-10-PC and install it manually on my Mac. It gets worse on the mobile platforms. So we probably can have an editor that makes things look the same on all platforms. But it will probably mean restrictions depending on what „other“ abilities the different platforms have that can not be unified. Or with other words: Maybe they have to crack some eggs to make an homogeneous omelette.

Just looked up the setup posted initially. If we talk about the Dell D3100 Dock, this piece of hardware is described by Dell as being Windows-only. Technically one can put a Mac into one of the USB 3.0-ports and connect an external monitor, but it is not supported by Dell. Dell advises when you use this Dock with external monitors to install drivers to Windows to avoid display problems. These drivers are not available for any MacOS version. Dell claims one can connect up to 3 high resolution monitors to a notebook by just one USB 3.0 connection, but I doubt that this piece of magic works seamlessly without the specific drivers. If one has this problem, maybe try another Mac-to-monitor connector. For testing purposes some cheap USB-C dongle with HDMI one usually has in his bag for travel will probably do.

Glad you posted on this older thread. What is new about this today, we didn’t already know about ? P.S. Running exactly the config claimed to be defective: MacBookPro with Touch Bar and external monitor, connected through a dock. However, no issue when switching monitors. Probably I should feel good to be the lucky one. Did anybody post this with Support, and got an answer ?

This causes me real pain. One half of my brain cries „how many more cool features do these Winnie’s try to steal from my Mac“, but then I go to the other desk, and the other half starts to sing „give it, give it to me“. One more vote !

OK, fine, we-who-stay-on got the message. Never stop a guy who is seriously going to take a walk, especially if he claims to be nauseous. P.S. On Mojave, still no issue.

Yes, some guys get all of the fun ... Currently on travel just with iPad and MacBook, so it will be a week and some until I can give it a try . Can’t wait to do so !

Seems to be ... Let us do some math: You have a customer base of 100 paying clients, making you 1.000 bucks a year. Now you discount for newbies, 5 will join, makes a revenue of 1.030 bucks the 1st year (40% discount), and 1.050 ever after. But your existing customers are unhappy. So you give the discount to everybody, and because everybody is so happy, you win 10 newbies by this. But your accountant is blown, because your income drops to 660, and when you expect it to go back up 1 year later to 1.100, you get the next revolution from your users. Plus even if not, you would need several years (could do the math, but you get the idea) to recover the revenue lost in the single year where you discounted. So we pay, use a workaround like the one above, wasting away a Sunday on hiding our prior existence, exporting and importing our data, or leave to another place, that tells us „Hi there, I have a discount for you (only the 1st year)“. And then you think, some times life sucks, but the sun is out, the birds are singing, the beer is cold and the girls are pretty ...

Maybe things have changed so far that there were releases on the Mac app in the meantime. But if you plan to upgrade to Catalina soon, probably it makes sense to wait for this OS and app to release, and upgrade both then. This is not to say the current SW should not be fixed (IMHO it should), but probably everybody in the Mac/iOS section at EN is right now occupied with getting this new stuff to the ramp and off. As I say, I have send a message, and wait to see when they are back to work tomorrow Californian time what will happen.

I think it is just for new customers. Somehow companies tend to spend to expand their customer base, which is how the word is turning. I am fine with this, as long as they do not forget the customer base they already have ... in the end it my money that helps others to join the pack 🤠

OK I‘ve send a direct mail to EN asking to look into this thread. We have 2 new posts here about it, they get input via Support as well, so maybe they have more to work with. I did never have the issue strongly on my MacBookPro, just once, back then before the new version got released, and I suspect there may be some weird interaction going on between EN and some other stuff that creates the problem. But as a user, I am happy when my machine is running. I did the uninstall-reinstall once, it did solve the issue, and I have no further idea what to do if this doesn’t help. Maybe open a support ticket yourself ?

When I read through this, I wonder whether this is looking for a solution, or venting some frustration about SW performance and EN company politics. I think we can work on the first, and have no possible contribution to the second.