Can't See box.com folder?

gdgross

Hi Peter/all -

I'm having an issue where the ST3 app on my iPad can no longer connect to the box.com folder on my iPad. See the attached picture when I try to browse to it within the ST3 app. The Box app itself works fine on its own, and I can see all the files there; however, I just can't access them within ST3 for some reason.

Any ideas what's going on? I've killed and restarted the iPad ST3 app several times, as well as power cycling the iPad itself, but no change. (Have not yet tried uninstalling and reinstalling anything tho...)

Side note, I also have ST3 installed on two computers, both of which are synced to my box account, and those installations can see the box folders just fine.

AnthonyB

Do you have the same issue if you just use the Files app?

I.e. is the problem an iOS problem between the Box.com app and iOS (which would result in the Files app also having a problem). If so, then the problem has nothing to do with ST3.

On occassion, I've had the Microsoft OneDrive app do the same and a simple uninstall/reinstall of the OneDrive app resolved the issue.

peter

I agree with @AnthonyB. This looks like a general problem with the iOS integration of Box. Make sure you can access your Box folder in the Files app and then it will automatically work in Stage Traxx.

gdgross

Sure enough, guys, I can't see the box folder in the Files app either.

I'll take it up with apple :-D Thanks!

gdgross

Turns out, deleting and reinstalling the box app clears things up.

AnthonyB

Glad you found a solution.

While I understand the way Apple have abstracted apps from 3rd party clound services by making iOS/Files the 'bridge', makes sense from a software architecture perspective (in theory), I've found it so be erratic and unpredicatable with Microsoft OneDrive, Google Drive, Box.com. That's just my experience of course.

So, either all of those companies write bad software, or
The iOS APIs that those 3rd party companies have to use are flaky, or
iOS is bad as acting as the 'bridge'.

I doubt it is the first option 🙂

peter

It still beats having to integrate each service separately with their own API into the app 😉

AnthonyB

peter Oh absolutely. The architecture makes complete sense... sadly the execution is lacking.