Not showing folders in Amazon S3
Using Flow 1.0.3 (561) with Amazon S3 only partially works. It is not showing all my folders within my main buckets.
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company marked this problem solved.
The best solutions from everyone
-
Build 572 is now available, and should (finally) resolve this issue.
A green light from you will turn this build into GM for official 1.0.3 release. :-)
I’m confident
The company says
this solves the problem
-
This issue should be resolved in the latest Flow nightly build, 571.
Let me know if it does, and 1.0.3 will be officially released.
I’m excited
The company says
this solves the problem
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Are you sure you're running build 561? There was a large fix for Amazon S3 in the build previous to it, 548, which many report to have fixed all Amazon S3 listing issues.
What, specifically, isn't showing up? Are there any special attributes / key-names to the buckets that are not showing up? -
Inappropriate?Yes. Unless the "About Flow" box is wrong.
-
Inappropriate?Can you share any more information about what isn't showing up?
It's pretty hard to diagnose what the problem could be without knowing what to look for on my end! ;-) -
Inappropriate?No problem. Flow connects fine with Amazon S3. I have two main buckets at the moment. Bucket_x01 and Bucket_x02. When I go into Bucket_x01 it shows two of the four directories. If I go further into Bucket_x01/Folder1/ it doesn't show all the directories either. This is repeated the deeper I go. Bucket_x02 has only one level of nested folders and works fine.
I used Transmit to manage S3 previously and using Transmit I am able to see all the folders within all the buckets.
To further test, I used Transmit to create a new Bucket_x03. I am able to create folders, add files, synchronize directories, and they are all visible in Flow just fine which is why I said that it mostly works.
It's just that I can't seem to see all the directories in that first bucket. -
Inappropriate?What are the names of the folders that don't show up in Bucket_x01? Do you notice anything different about the key-names of those that don't show up compared to those who do?
-
Inappropriate?There isn't anything odd in the naming at all. As an example two that don't show up in a root bucket (Bucket_x01) are Flightlevel Logbook and EndNote. Nothing odd about them, they just aren't showing up.
I have a directory called EagleFiler that shows up (in the Bucket_x01), but when I go into it, I only see one directory called Alaska 2006 in it. There are actually several directories in there, one is called Alaska 2007, another called dbl, another Software - Storage. So nothing really odd in those names. -
Inappropriate?Build 561 is now available and fixes a few issues with encoding paths in relation to Amazon S3. Let me know if this fixes your issue.
That being said, thus far I have not been able to reproduce the behavior you're talking about. If the issue still persists, the following will let me see exactly what's going on:
- Open Terminal, in /Application/Utilities/Terminal
- Assuming you have Flow in your applications folder, type:
/Applications/Flow.app/Contents/MacOS/Flow - Click the "Help" menu, then "KTLog Debug".
- Click "Add Domain". Double click the "New Domain" text and rename it "Input Stream". Set the Level to "DEBUG"
- Connect to your Amazon S3 account and navigate to a directory that does not show all of your folders.
- Copy the output into a post here, or to into an e-mail to support@extendmac.com
-
Inappropriate?I sent you the debug information to support@extendmac.com because it's a long output.
I’m excited
-
Inappropriate?Just discovered the problem, and am working on a fix. Should be available later today!
I’m happy
-
Inappropriate?This issue should be resolved in the latest Flow nightly build, 571.
Let me know if it does, and 1.0.3 will be officially released.
I’m excited
The company says
this solves the problem
-
Inappropriate?Almost there. It does show all the directories now, but now it is showing multiples of the directories that had missing directories.
I’m amused
-
Inappropriate?Hmm.. Are the multiples at the same hierarchal level?
As in:
bucket
-directory1
-directory1
-directory2
or...
bucket
-directory1
--directory1
-directory2 -
Inappropriate?Same hierarchial level.
One of my folders shows up five times, with each one with a different Modified date and time.
I’m confused
-
Inappropriate?Can you do the steps I outlined above (with enabling the debug logging), and send it to support@extendmac.com again?
Thanks! -
Inappropriate?Just a quick note –– instead of "Input Stream", you can debug "Protocol" –– it'll give much clearer and concise results that are easier to analyze. :)
-
Inappropriate?Build 572 is now available, and should (finally) resolve this issue.
A green light from you will turn this build into GM for official 1.0.3 release. :-)
I’m confident
The company says
this solves the problem
Loading Profile...




