Steve L.32 Helpful | Level 6

I've restructured the Dropbox authentication flow slightly in light of the iPhone / iPad differences I found. I’ve used Dropbox in this App since 2011, so I’m surprised I didn’t see this issue earlier, although I must note that the viewDidAppear:animated code was added 2017.05.22 - this was my great API 1 --> API 2 commit!…

Wasn't finished with last post, continuing: I assume the real problem is that extractfromDAuthURL:url is called twice and thus the stored nonce doesn't match the current nonce. Also, I munged the redaction in the log entries previously, so here they are again. 2017-11-11 17:32:29.380496-0500 Krypton[3454:894607]…

In the DB code you pointed to there is an if() in function if (state.count == 2 && [state[0] isEqualToString:@"oauth2"] && [state[1] isEqualToString:nonce]) { state.count is == 2, state[0] is == "oauth2", but state[1] is != nonce. Do not know what it means at this point, but that is the failure.

@"Greg-DB" wrote:I'm not aware of any other reports like this, so we'll have to investigate. First, can you share: * the version number of the Dropbox SDK you're using Not sure exactly how to determine that (guessing 3.1.0), I found a plist file in the source, here it is: * the version number of the official Dropbox for…

And the log error is: Auth Error: Error:[ErrorType: 6 ErrorDescription: Unable to verify link request

Goodness! After one hour waiting for review, and one hour under review, the macOS version of the App is on the Store. 2 hours is a new record for me. The average user will only have 1 copy of the App on their machine so authentication should work normally. I think I'll go check that box indicating that I know about the 28…

Another update: The macOS version of my App is waiting for review, but I still have reservations about the Dropbox V2 API OSX authentication scheme. To get this more-or-less working version I spent many hours spread over many days trying lots of things. In particular I built a static library, and even though ar showed that…

FWIW, the iOS version of my App just passed review and is on the App Store. One down, one to go. Thanks for all your help so far.

The iPhone and iPad iOS version of my App with Dropbox V2 API is waiting for review, we’ll see if they pass muster. But I still cannot archive the macOS version for review. Should I perchance try to build a static library. I ask because I continue to see confusion when it comes to resolving the real path of the dynamic…

OK, thanks, project and my release notes updated.

FWIW that trick only works on iOS, the macOS version still gets the dynlib error as reported here, unfortunately.

Hmmm. After hours of hacking I tried adding the framework an an embedded binary, and lo and behold the App now runs on a device: That seems to give me TWO instances of Linked Frameworks now. In the DB docs, for method #3 Xcode subprojects the instructions are very specific: 1) for iOS add the framework as a Linked…

Thank you Greg, perfecto! I can cancel uploads and downloads on the iOS simulator. But when I try to run my App on a real device (iPhone 7) I get a dynlib error similar to what happens when archiving the macOS version of my App ): I am again using the Xcode subproject method. So I am stuck again ... Thanks, Steve

Why thank you. I went back to method #3 Xcode subproject and I can once again build and run on my Mac, link and unlink, up-and-download, delete, etc.. When I archive, my typical MO is to upload directly to the App Store. Often I will Export the archive as a macOS App for a final dry run - it's this executable that fails.…

So I canned the Xcode subproject method, and re-did everything using method #2 Carthage only. Now I cannot even run in debug mode, I get the same errors: 1) cannot load Dropbox framework, and 2) Dropbox code signing error. Has anyone actually gotten a macOS app using Dropbox API V2 on the Mac App Store? Is this likely an…

Using the Xcode subproject method BTW. Is there a special Copy Files build setting or something I can use .... (don't see one in the docs). Thanks.

Nevermind :) I spent all morning working on the macOS version of my App. But with DBRoulette I used the iOS version and mistakenly imported the macOS subproject. Sigh, old sux.

FWIW the documented path to the Xcode subproject differs from what I found, if that matters: Salamander:DBRoulette lusol$ dir Carthage/Checkouts/ObjectiveDropboxOfficial/Source/ObjectiveDropboxOfficial/ObjectiveDropboxOfficial.xcodeproj ls:…

I too am finding it extremely difficult in making this v2 transition. My needs are very simple: my v1 app queries metadata, and uploads and downloads files. The old DBRoulette example was simple to understand, all I needed was a key and a secret, and authentication just worked. I never even heard of OAuths and endpoints…

Fair enough, thank you. For me, an old guy, I need to spend my time on my Apps proper, so really appreciated simply droppping an officially built, fully supported framework into my Xcode project, without having to worry did I screwup building yet another few thousand lines worth of code. Learning curves get really steep at…

I keep re-visiting this v1 -> v2 project. First there was no Objective-C path, and now there are 3 "methods". Why is it not possible to just provide a Framework as in v1? I have no idea what CocoaPods or Carthage is/are but it seems I must install at least Carthage on my Mac, which I have no desire to do, to do anything.…