iPad if older client can't log in

[Apmcomp]

Today, I purchased the iFolder client for the iPad.
I have my ifolder server set to only accept https connections for
iFolder. In addition, I don't have a publicly signed certificate.

The iPad client has check marks for Use Secure (https)SSL and
Certificate publicly signed. When I check these the https and test
connection, connection is made. However, when I save the settings and
try to connect to the server, I get an error saying server not
found.
I got back into the connection information and find the Use Secure
Server is no longer checked off.

I don't see anywhere else to get this to save.

Can someone please tell me a.) if this is normal behaviour and b.) if
this has been seen? I don't see anywhere else to contact the authors
for any technical support for this paid application.

Please advise.
Regards,
Paul

Paul M. Muhlbach, A+, CNA, MCSE, MCT
Camrose, AB

[Roger Moffatt]

Hi Paul

You can always reach us from the contact us link at ifolder.mindsizzlers.com, or the support links on iTunes ... or this forum.

So it looks as if iOS5 has broken the keychain code resulting in account settings not saving correctly. It seems that prior to iOS5, we could save arbitrary data types in some of the keychain fields, but that now the data typing is more rigorously enforced by the operating system and so our storage of the https and certificate flags are failing. 

Unfortunately there is no workaround, so at the moment upgrading to iOS5 will break this app.

We're running some more tests to check that this is all that iOS5 has broken and will issue an update to Apple over the coming days once we have everything working again.

Roger

Mindsizzlers LLP

[Hans]

Hi Roger and Paul,

 

runing my iFolder iPad client seamlessly.

The only thing I deactivated was "Require Verifies Certificates".

 

This is not a migration, but a new install onto the iPad 2 with IOS5.

Running against the iFolder delivered with OES2, means 3.8.4.

 

Regards

Hans

 

>>> Roger Moffatt<roger....@gmail.com> 24.10.2011 09:54 >>>
Hi Paul

[Roger Moffatt]

Thanks Hans

Hmmm ... it could then be that it's building under the new iOS5 SDK that is showing the keychain issue, rather than iOS5 per se. I'll investigate further.

Roger