Robin2 4 Posted October 5, 2020 Share Posted October 5, 2020 The iOS webclipper is saving each clip to the default notebook instead of the notebook I specify in the iOS sharing extension dialogue. I've repeated this several times with different notebooks, and it's happening every time I try to save anything on my iPhone. Each time, I have to then manually move the clipped note into the correct notebook. I'm using the most recent Evernote update on iOS14. 1 Link to comment
Level 5 PinkElephant 8,795 Posted October 5, 2020 Level 5 Share Posted October 5, 2020 Can confirm this - it does not pick the notebook selected, but (in my case) the Inbox, which is default. IOS 14.0.1., EN 10.0.3. Would you mind to issue a support ticket, and share the result ? Link to comment
Robin2 4 Posted October 5, 2020 Author Share Posted October 5, 2020 6 minutes ago, PinkElephant said: Would you mind to issue a support ticket, and share the result ? Done. 1 Link to comment
Level 5 PinkElephant 8,795 Posted October 5, 2020 Level 5 Share Posted October 5, 2020 Just tried this by sharing a pdf created with ScannerPro on my iPhone. There the title, notebook and tags (!) are entered in a screen belonging to the scanner app before hitting the share button. The new note was created in the designated notebook, carrying the tags and title. It seems the sharing API used by the readdle app is still working as it should. Link to comment
Ex Employees Jaya Shekarraju 75 Posted October 5, 2020 Ex Employees Share Posted October 5, 2020 @Robin2 Thank you for your patience. We are working on fixing this issue. Link to comment
Level 5* DTLow 5,744 Posted October 8, 2020 Level 5* Share Posted October 8, 2020 On 10/5/2020 at 5:57 AM, Robin2 said: The iOS webclipper is saving each clip to the default notebook instead of the notebook I specify in the iOS sharing extension dialogue. Confirmed - Fixed in v10.0.4 Link to comment
Level 5 Solution Shane D. 1,826 Posted October 9, 2020 Level 5 Solution Share Posted October 9, 2020 Hi All, As mentioned above, we believe this issue has been fixed in Version 10.0.4. If you have not already, please update to this version, and let me know if you still encounter this issue. Link to comment
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now