Used latest CocoaPod (with use_frameworks!) & Xcode 6.4 with Swift, and when printing out any thing in LLDB, if I import ENSDK in the Swift-ObjC Bridging header like:

import <ENSDK/ENSDK.h>

I get the following errors:

error: Error in auto-import: failed to get module 'Noter' from AST context: /Users/hyou/Dropbox/dev/iOS/Pendo/Noter-Bridging-Header.h:20:9: error: 'ENSDK/ENSDK.h' file not found

import <ENSDK/ENSDK.h>

    ^

failed to import bridging header '/Users/hyou/Dropbox/dev/iOS/Pendo/Noter-Bridging-Header.h'A fatal parse error has occurred. LLDB may become unstable; please restart your debug session as soon as possible.

Otherwise, if I import ENSDK like:

import "ENSDK.h"

I get the following:

error: Error in auto-import: failed to get module 'Noter' from AST context: /Users/hyou/Dropbox/dev/iOS/Pendo/Noter-Bridging-Header.h:19:9: note: while building module 'evernote_cloud_sdk_ios' imported from /Users/hyou/Dropbox/dev/iOS/Pendo/Noter-Bridging-Header.h:19:

import "ENSDK.h"

    ^

:1:9: note: in file included from :1:

import "/Users/hyou/Dropbox/dev/iOS/Pendo/Pods/Target Support Files/evernote-cloud-sdk-ios/evernote-cloud-sdk-ios-umbrella.h"

    ^

/Users/hyou/Dropbox/dev/iOS/Pendo/Pods/Target Support Files/evernote-cloud-sdk-ios/evernote-cloud-sdk-ios-umbrella.h:6:9: error: 'EDAMErrors.m' file not found

import "EDAMErrors.m"

    ^

/Users/hyou/Dropbox/dev/iOS/Pendo/Noter-Bridging-Header.h:19:9: error: could not build module 'evernote_cloud_sdk_ios'

import "ENSDK.h"

    ^

failed to import bridging header '/Users/hyou/Dropbox/dev/iOS/Pendo/Noter-Bridging-Header.h'A fatal parse error has occurred. LLDB may become unstable; please restart your debug session as soon as possible.

The functionality that authorises by switching to the Evernote app appears to be broken. Probably because of a bug in the Evernote app?

The app switch happens but inside the Evernote app the option to grant access is never displayed. This happens for two apps that I have been working on and the same thing also happens with other apps such as Scanbot. The Evernote app is launched but then nothing more happens.

I have tried on iOS 9 and iOS 10. Evernote app version is 8.3.356604

I want to use the new evernote-cloud-sdk-ios as a framework with CocoaPods but it doesn't work.

1. There are non-modular header file usages in ENXMLUtils.h and ENXMLSaxParser.h

   import <libxml/xmlstring.h>

   import <libxml/tree.h>

2 The mysteries error of not building "Objective-C" module "evernote_cloud_sdk_ios"

And yes, I have used CLANG_ALLOW_NON_MODULAR_INCLUDES_IN_FRAMEWORK_MODULES=YES

Please fix or give me hints for workarounds.

Repro steps

• Try to login with Evernote (ENSession.shared.authenticate(with:preferRegistration:completion:))
• A login view controller is presented by the Evernote SDK
• Input your email, then tap on Continue
• It used to show the password form before, but now it turns into the white screen.

Does anyone have the same issue?

I have implemented the SDK integration for my iOS app, where web view is pushed for login and authorise the account. In this screen user can select the authorisation time period in popover, selecting the option from list multiple time causing the app to crash with error,

Application tried to represent an active popover presentation: <UIPopoverPresentationController: 0x18f66470>

*** Terminating app due to uncaught exception 'NSGenericException', reason: 'UIPopoverPresentationController (<UIPopoverPresentationController: 0x18f79b60>) should have a non-nil sourceView or barButtonItem set before the presentation occurs.'

*** First throw call stack: (0x24e8d49f 0x32945c8b 0x289ee59f 0x2861ce03 0x2861badb 0x283c9a25 0x2834582b 0x24e53d95 0x24e51453 0x24e5185b 0x24d9f3c1 0x24d9f1d3 0x2c1740a9 0x283aefa1 0x2ee21 0x32ec5aaf) libc++abi.dylib: terminating with uncaught exception of type NSException

I just need record note for my reading book,how can i repeatedly update this one note programmatically(point to a particular note in the Evernote service)?

Creating a new project, and trying to install SDK using CocoaPods 1.2.0 gives me the following error.

[!] Unable to satisfy the following requirements:

- `evernote-cloud-sdk-ios (~> 3.0)` required by `Podfile`

None of your spec sources contain a spec satisfying the dependency: `evernote-cloud-sdk-ios (~> 3.0)`.

You have either:
 * out-of-date source repos which you can update with `pod repo update`.
 * mistyped the name or version.
 * not added the source repo that hosts the Podspec to your Podfile.

Note: as of CocoaPods 1.0, `pod repo update` does not happen on `pod install` by default.

Running pod repo update doesn't help.

My app support App Extensions (Share/Action). In the main app user already logged in and the extension should just use the auth token from the main app.

To enable this, I'd need to enable shared key chain. Currently Evernote SDK did not expose ENCredentials, ENCredentialStore and ENSSKeychain. Which make configure the key chain outside impossible.

Also, ENSSKeychain seems to be an older vendored version of SSKeychain. Newer versions of SSKeychain support configuring the App group by using SSKeychainQuery.

This probably a common scenario (as seen in #65). I'd love to send a PR to fix this. However I'm not sure where should I get started. Your input is greatly appreciated.

Hello, @everic,

Is there a possibility to share [ENSession sharedSession] between my main app and my app extension?

Otherwise I have to ask a user to login twice - once in the main app, second time with the first execution of my app extension?

Thanks in advance, Ilia

Is there any way to get the userStore from the ENSession? It looks like it's in the .m, but not exposed in the .h. Is there an easy way for me to get access to it from a sharedSession?

Now i debug by the developer token. But i need to switch call method: [ENSession setSharedSessionConsumerKey:consumerSecret:optionalHost:],and always get 401 statusCode,how to make it work?

Corresponding to Apple rule : https://developer.apple.com/news/?id=mdkbobfo

I'm using the Evernote pod in my iOS apps. When logging in to Evvernote, in the application can create account from your SDK. My Question: Can Evernote SDK support account deletion since it's required by Apple?

Thank you in advance.

This API is deprecated and thus any app trying to launch Evernote will not function as of last week. - (BOOL)openURL:(NSURL*)url API_DEPRECATED_WITH_REPLACEMENT("openURL:options:completionHandler:", ios(2.0, 10.0)) NS_EXTENSION_UNAVAILABLE_IOS(""); Thanks @zonabi @juanarzola

Repro steps

• Try to login with Evernote (ENSession.shared.authenticate(with:preferRegistration:completion:))
• A login view controller is presented by the Evernote SDK
• Tap on Continue with Google
• Observe error: "403 disallowed_useragent" Google can’t sign you in safely inside this app. You can use Google sign-in by visiting this app’s website in a browser like Safari or Chrome.

This issue is affecting our app Genius Scan and I could also reproduce it with @agiletortoise Drafts App.

Solution

The problem is likely that the login must happen in a safari controller and not in a webview.

Repro steps

• Try to login with Evernote (ENSession.shared.authenticate(with:preferRegistration:completion:))
• A login view controller is presented by the Evernote SDK
• Swipe down to dismiss this screen
• Try to log in again
• Observe error

This issue is affecting our app Genius Scan.

Easy fix

The problem is due to this new "swipe down to dismiss" gesture on modal view controllers.

https://stackoverflow.com/questions/56459329/disable-the-interactive-dismissal-of-presented-view-controller-in-ios-13

Evernote users which use a linked Google account to authenticate with the Evernote service (via "Continue with Google" can no longer authenticate using the Evernote SDK's authentication process.

Because the SDK uses the deprecated UIWebView to present the authentication flow (see also issue #170 regarding pending App Store rejection over the use of UIWebView), when redirected to Google to sign in using the "Continue with Google" button, the user will receive a "403 Error: disallowed_useragent" message the authentication process will be halted.

Additionally, Google provides the message:

Google can't sign you in safely inside this app. You can use Google sign-in by visiting this app's website in a browser like Safari or Chrome.

It is not possible to do so as part of the OAuth process, however.