nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Child Item

Dropbox Core API on Android and startActivityForResult

asi d.

I am trying to switch from SyncSDK to Core API. Everything going smoothly apart from your sample about picking up authentication result on onResume method of the activity. Shouldn't Core API Android helper follow Android design pattern and deliver result to activity after calling startActivityForResult? SyncSDK does this.

onResume works too but it is unnecessary to keep checking authentication result whenever user opens my settings activity.

Am I missing something?

Find more posts tagged with

API

Abuse

Comments

Greg-DB

The Sync and Core SDKs do handle the app authorization flow somewhat differently as you pointed out. I'll be sure to send this along as feedback, but for now we recommend implementing the authorization flow as shown in the tutorial.

asi d.

Thanks very much for responding. I have implemented as in your tutorial but as I've stated above, handling response from authorization is not optimal and does not follow Android design pattern.

I will wait for future updates