migrating from API 1 to 2 - how do I know if I have OAuth 1 tokens?

Yea, you can use DBOAuthManager.clearStoredAccessToken for specific tokens, or DBOAuthManager.clearStoredAccessTokens for all tokens.

Ok, thanks Greg.

Also, when I use DBFILESgetMetadata, is there any way to tell if the path is a file or a folder?  In the old SDK there was an 'isDirectory' field of the metadata structure, but I don't see one for DBFILESMetadata. ?

Also, if it IS a folder, then how do you access the contents of the folder?  With the old SDK I uses a loop like this:

for (DBMetadata *file in metadata.contents)

Thanks

Bob

OK thanks, and how would you access the contents of the folder, is that included in the metadata or do you have to issue another call to get that?  Would I have to use listFolder?

Hey Greg,

  If getMetaData returns an error, how do you retrieve the error information from DBFILESGetMetadataError?    It looks like it only contains a path and a tag, and I can't tell what the tag is.  The docs say it represents the "union's current tag state", but it doesn't show any values.  Is there some other way to get information about why it failed or what the error is ?

Thanks,

Bob

Thanks for the reply.  I get that I can use the 'is' commands to check the error, but in the case of the metadata, there is a path and a tag.  The path is pretty self evident.  But what is the tag?  The docs don't seem to provide any details about what that is.  I'm just wondering in the case of an error, how I would go about determining the cause or reason.  The path I already know.  And it doesn't look like the tag tells me anything.  Does that make sense?

Thanks!

The "tag" is the way the API describes which member of the union the object is. The SDK uses it to determine what the "is" methods return. So, you don't need to access tag directly, as long as you use the "is" methods.

To get the actual error information, use the respective field. For example, DBFILESGetMetadataError.path gives you a DBFILESLookupError, which itself has various "is" methods to tell you which error it was (and so on, for any further nested errors).

Oh, I see, the path contains the error information. I had assumed the path was just the file pathname.

Thanks!