omnifett / iphonefrotz

Automatically exported from code.google.com/p/iphonefrotz
Other
0 stars 0 forks source link

Issue 96 may not be resolved... #107

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1.Start local WiFi (on PowerMac G4 Airport to 2nd gen. 32 GB iPod Touch)
2.Start WiFi on the iPod Touch.
3.Switch to Frotz and go to the File Server page - hit the start button.
4.Start up FTP client on the Mac and open connection window for the IP
address given by Frotz.
5.Try to drag and drop the .z5 files from the Mac folder's window (in FTP
client) to the (Frotz) IP window.

What is the expected output or behavior?  What do you see instead?
Hoping for some sign - either in Frotz, but preferably in both Frotz and
the FTP program, that a file is being transferred (and then completed).
Instead, the FTP program give an error message (-999960 I think - is that a
timeout?), and Frotz never even acknowledges any attempt to upload the
file(s) to the iPT.

What version of Frotz are you using?
1.4.1

What version of iPhone/iPod Touch OS? (2.2.1, 3.0, 3.1.2, etc.)
3.1.3

What device model are you using (iPod Touch 2nd gen, iPhone 3G, etc.)
iPod Touch 2G, 32GB

Please provide any additional information below.

PowerMac G4 (AGP, 1.25 GB actual RAM, standard Airport card (which works
fine for browser to reach other internet locations), running Mac OS X 10.4.11)

If I could put the files on a server and get them with Frotz via a local
WiFi (at restaurant) to get the files into Frotz, that would be tolerable.
Just getting frustrated that nothing seems to be happening (other than the
error message)...

Original issue reported on code.google.com by jimrcgmo2002@gmail.com on 26 Apr 2010 at 4:34

GoogleCodeExporter commented 8 years ago
What FTP program are you using?

Please try using the http URL with Safari instead of FTP and let me know how 
that works.  The web interface is 
much easier to use.

Original comment by spath...@gmail.com on 26 Apr 2010 at 4:45

GoogleCodeExporter commented 8 years ago
Interarchy 7.5.3, running under Mac OS X 10.4.11. 

Also, your contact email bounces... You should update it, maybe (if you want 
feedback).

Original comment by jimrcgmo2002@gmail.com on 27 Apr 2010 at 2:35

GoogleCodeExporter commented 8 years ago
Well, thanks - Safari did work, though Firefox (browser) nor Interarchy (FTP 
client)
would (go figure...). Shame that finding out how to get Frotz to work with 
uploads
(and other things) couldn't be posted on here somewhere (like a more complete 
FAQ
drawn from the various issues - especially the solved ones - or a PDF file we 
could
download. Or would the App Store object to that, I wonder? ;-)

Thank you for the help! (Do update your contact email so it works, please)

Original comment by jimrcgmo2002@gmail.com on 27 Apr 2010 at 3:16

GoogleCodeExporter commented 8 years ago
What contact e-mail are you talking about?  My main contact email works fine 
because it is how I get 
notifications of new comments here.  It is spelled out as "ifrotz at gmail dot 
com" on the support page to 
reduce spam from automated email collection.  If there is another address 
listed elsewhere, I am not aware of 
it... please let me know.

I tested FTP support originally using Cyberduck, Fetch, Interarchy, WinFTP, and 
command line ftp on Mac, 
Linux, and Windows.  It looks like some problems crept in with the latest 
update because I was forced by 
Apple to rewrite part of it that had been working fine because it was calling 
an unblessed API.

I tested Web support on Safari and Firefox on Mac and Firefox and IE on 
Windows, and Firefox on Linux, on 
my home network, network at work, and free wi-fi at a local coffee shop.

There definitely seems to be a new issue with FTP in the latest release I 
haven't nailed down yet.  
But many problems with file transfer are due to local network configurations 
and name server/firewall issues.
Posting this issue as a FAQ would likely not be useful to anyone else because 
they don't have your particular 
network setup, and we didn't actually figure out the root cause of the FTP 
issue.  I do already recommend 
using web transfer over FTP both in the Info screens and the support  page.

I have no idea why Firefox wouldn't have worked if Safari did, because that's 
obviously not a network 
connectivity problem.  What kind of error or bad behavior did you see?

Original comment by spath...@gmail.com on 27 Apr 2010 at 3:51

GoogleCodeExporter commented 8 years ago
Is this the same defect as bug 101?

Original comment by timur.t...@gmail.com on 4 Jul 2010 at 5:15

GoogleCodeExporter commented 8 years ago
>Comment 5  by timur.tabi, Yesterday (24 hours ago)
>
>Is this the same defect as bug 101?

At least, not exactly, since I'm using an iPod Touch and not an iPad (which 101 
appears to describe that problem occurring with)...

Original comment by jimrcgmo2002@gmail.com on 5 Jul 2010 at 6:00

GoogleCodeExporter commented 8 years ago

Original comment by spath...@gmail.com on 5 Nov 2010 at 5:31

GoogleCodeExporter commented 8 years ago

I was never able to reproduce this problem and no one else reported it, so I'm 
closing the issue.
Re-report against 1.5 if it's still happening to you and you have any more 
information about the issue.

Original comment by spath...@gmail.com on 5 Nov 2010 at 5:32