Jump to content

MountainMan01

Level 2
  • Content Count

    22
  • Joined

  • Last visited

Community Reputation

11 Neutral

1 Follower

About MountainMan01

Recent Profile Visitors

771 profile views
  1. Yep... still on the radar. Been a problem for 2 years. 2 bugs have been opened (and are still open) on this issue from my Premium membership. The first happens as described. The second is when you try to set a tag for multiple notes. If you hit the backspace button when typing a tag, it sometimes just removes the tag, so you need it to do it multiple times until it gets set. Yes, Evernote has the ability to code around it. They have fixed it in betas, then they taketh away on the release with the claim that its an "apple" bug. Interestingly I have never seen this "bug" from apple in any other application. It seems to be Evernote specific, so they are using some API that is specific to what they are doing. I am guessing its for this reason that Apple has put such a low priority on it... and now we are Mac OS Sierra soon, so I guess Apple won't be fixing this "bug" any time soon. Bottom line is Evernote doesn't give a cr@p about their paying customers as they have shown that they can fix this bug, but then decide not to and point at Apple. They don't understand that sometimes you need to code around so-called-bugs to make your customers happy, but we all know that Evernote doesn't get customer service. At this stage, I don't really care if it gets fixed or not. They raised their prices to a ridicules amount, so I am in the process of migrating my notes to OneNote before my renewal date goes into effect in February. They lost me as a customer due to their sh*tty customer support and ridicules pricing. You asked if there is a work around. Kind of. Type your tag up until you get to the "-". Type a "x" instead. Then hit backspace and continue with the "-". You will need to do this every time you hit a "-" in your tag if you have multiple "-"s in the tag name. Other than that, you are stuck. I would recommend looking at other alternatives anyways as Evernote looks like they may not be around very long. I prepared for this by OCRing every PDF knowing I would need PDF search capabilities in other product. I'm prepped to move... so should everyone else.
  2. I have to laugh at the release notes from 6.7.1: "Version 6.7.1: Fixed various bugs that affect users on OS X 10.10.x" Whoops... all but this bug ;-) Evernote.. when are you going to code around this one?
  3. Evernote's I didn't mean to lash out at you. You were just trying to help. I am just a frustrated user and customer of Evernote due to this bug and getting a line cr4p from them when I check the status or some lame excuse from them on why it isn't fixed, or pointing fingers at Apple. I have just had it from this company. They need to learn a thing or two on how not to be a hipster support group and about how customer service works.
  4. That's hog wash and hand waving. Evernote fixed it in 6.2B and 6.6B. My exchange with support in my previous posting underscores that it can be coded around. Its a ridicules bug (I am speaking as a software developer) that most certainly can be fixed, and they have fixed it before. Heck, from your saying the best we can do is not use dashes... why not go all the way and lets just not use tags, right? That gets rid of the problem completely! Right? ;-) Sorry, but your statement is flawed. I have a LOT of tags and everyone of them uses a "-". I'm not going to go back and change every single "-" to a ".". If i have to retype every tag, then its not worth the time or headache. Sure, if I was to do this from the beginning and knew this would be such an insane problem, I sure could have used a ".", but that's a day late and a dollar short. I pay for Pro... I expect that they fix simple bugs... this has been open for 2 years... and they continue fix then regress it. That's bad customer service and its bad faith.
  5. I'll give you news... and it's not good. So first of all, Evernote seems to be the only application that has this issue (at least from my perspective). They claim its an Apple bug, but I have my doubts. They have fixed it 2 times, then subsequently pulled the fix. It was fixed in 6.6b of which I commended them on the fix. After they fixed in in 6.6B, I sent them a note telling them that they finally fixed it with a hearty "thanks". Response from Nick L. in support on 3/21: "Thank you for writing us back. This bug is still opened by Apple, but we have managed to code around it. This should no longer be an issue moving forward." But low and behold... in the 6.6 release, it was back! So I reopened their ticket and stated: "As a FYI, 6.6 Beta had this bug fixed. Your official release of 6.6 regressed and the bug is back. When will you guys lock your code so it stops showing itself. If I knew it regressed, I never would have upgraded." and Nick L. proceeded with the following response: "We're currently working with Apple to get the bug resolved on their end so we can provide a stable fix. At this time I do not have an estimated date of when this will be fixed." Bottom line is their support is a freaking disaster area. This is what happens when you let hispsters decide on these sorts of things. ;-) They giveth, then they taketh. My analysis is they are using some obscure crapola in Apple's API (that nobody uses) rather then commit the "workaround" and do it so its usable. IMHO, this issue is a blocker and their devs leave a lot to be desired, with their tickets and support being even worse. I am seriously looking at M$ OneNote at this stage and pulling my Pro subscription... this software is quickly becoming pure ***** and I won't pay for support with bugs that are open for over a year. They should be ashamed of themselves.
  6. Yeah, but you fixed it in a beta ;-) This tells me you have some control over it ;-)
  7. Just an update. This looks like an Evernote bug as its fixed in 6.2.2 Beta 2. Just putting this here for anyone else who is experiencing this issue.
  8. Hello? Any Evernote folks out there? You guys wanna share Apple bug RDAR number with the community for Yosemite so we can report the regression for El Cap or you guys want us to pound it as a bug for Evernote?
  9. Hi, it looks like this bug has returned to El Capitan. Its the exactl same problem. Do you have a copy of the bug on the Apple side so that it can be reported again?
  10. Yep... looks good ;-) Why didnt you guys say so in the beginning? I could have given Apple the hard time instead of you. ;-)
  11. 6.0.8 released and bug still exists. We are nearly at 6 months and nothing has been done. Evernote folks, do you have a time frame on the fix?
  12. Yep agreed. I am guessing Evernote devs use Mtn Lion or are Windows users. Because based on this: https://www.gosquared.com/global/mac/yosemite/#beta 42% (as of 3/3/15) of their mac customers need this fix. I would think that would be considered a priority.
  13. 6.0.5 is out... and bug is *still* not fixed. Can we please get an answer to when this is going to get fixed?
  14. *tap* *tap* *tap* Is this microphone working? 6.0.3 released today and this bug still exists. Being a software dev myself, this one cannot be difficult to fix... time frame for fix would really be appreciated... Hello? Beuller?
×
×
  • Create New...