kenknight
1 Nickel

url schema for iOS not working

url schema for iOS not working

Hi all,

Ok, I believe I have the documentation located here pocketcloudsupport.wyse.com/e...ys-url-schemes memorized I have read over it so much. I'm not saying I've missed something but at any rate, I cannot get URL based files to work on the iPad, however, the same file will launch on an Android tablet. The problem there is that the android is running in 16 color mode while the a static connection to the same server using iPad is full color.

No matter what code I put in the test app to launch the pocketcloud app on iPad it comes back with an "Invalid RDP file" saying it must be UTF8 encoded and must have a 'full address' line which it meets all these requirements. Again, android on the same file works great. I have tried URL encoding and everything else I can think of... at this point I'm out of ideas. Also it is probably worth mentioning that the same file and path works fine when launching with iTapRDP, but we feel pocketcloud is MUCH faster and operates more smoothly.

Thanks,
Ken

0 Kudos
11 Replies
Chris-2015
3 Zinc

RE: url schema for iOS not working

Ken - Can you send me your file and let me know what URL you are using?

Thanks,

Chris

0 Kudos
kenknight
1 Nickel

RE: url schema for iOS not working

headed your way!

Thanks,
Ken

Actually I need a way to send it to you as I can't post the info here in the forum. Can you send an email to  kknight -at- propertyboss.com ?

0 Kudos
Highlighted
Chris-2015
3 Zinc

RE: url schema for iOS not working

Hi Ken - You can e-mail it to iossupport@wyse.com
ATTN Chris

0 Kudos
thwang-2015
1 Copper

RE: url schema for iOS not working

Hi
I am having the same issue with version 2.2.214 of PocketCloud. In a previous version the same launch of PocketCloud was working.

Can anyone confirm this problem ?

ThomaS

0 Kudos
Chris-2015
3 Zinc

RE: url schema for iOS not working

Thomas - There is a fix in our new build which may address your issue. It is due out in 2-3 weeks.

-Chris

0 Kudos
kenknight
1 Nickel

RE: url schema for iOS not working

Red face Still having problems with this

Hi all,

I need details on exactly what pocketcloud expects to receive from the call to the passed in URL. Things such as MIME type, document encoding etc. I've have tested until I'm blue in the face and this thing has yet to work. However, if I pass the same url in a browser and let it open on my desktop, with the exception of the pocketcloud specific tags, it will launch remote desktop and make a connection to the correct server with the correct username.

The URL format (example) that I'm using is like this;

pocketcloud://mydomain.com/tablet_loging.php?sess=GUID_String

This will return a valid rdp file (or at least what I'm calling a valid file), yet pocketcloud responds with an invalid bookmark URL or something of that nature.

The rdp files have to be delivered dynamically which is why I've got an app that authenticates them and then passes that session guid back to the server to hand out the correct RDP file for that user.

Any suggestions would be great as we'd like to get this rolled out sooner rather than later and sadly we're already into the later part. BTW I'm using this line of code to launch inside the iOS app

[UIApplication sharedApplication] openURL:[NSURL URLwithString: launchURL]];

Thanks,
Ken

0 Kudos
Chris-2015
3 Zinc

RE: url schema for iOS not working

Hi Ken,

Our developers provided the sample PHP code below for you to try: 

 

<?
header("Cache-Control: no-cache, must-revalidate");
header("Pragma: no-cache");
header("Content-type: application/x-rdp");
header("Content-disposition: inline; filename=mydesktop.rdp");

$param = $_GET['address'];

echo "full address:s:$param\n";
echo "username:s:someusername" 
?>

0 Kudos
kenknight
1 Nickel

RE: url schema for iOS not working

Beautiful. I'll give it a try this evening. I'll also do a packet capture on a desktop to see exactly what is being passed down from the server.

Thanks,
ken

0 Kudos
kenknight
1 Nickel

RE: url schema for iOS not working

Just did a packet capture and I see that my code (which is actually not in php.. I just used that as an example earlier) returns the following tcp stream;

================================================== ================
HTTP/1.1 200 OK
Content-Length: 152
Content-Type: application/x-rdp
Server: Microsoft-IIS/7.0
Set-Cookie: AWP_CSESSION=6BC739F8920C006915D382B1968C888C2E1A8 4B3; path=/
WebDevSrc: MEM application/x-rdp
Content-Disposition: Attachment; filename="3690986a861c449c977394b80230724c.rdp"
X-Powered-By: ASP.NET

Date: Tue, 25 Oct 2011 23:31:58 GMT

username:s:xxxxxxxxxxxxxxxxxxx
pocketcloud password:s:xxxxxxxxxxxx
full address:s:xxxxxxxxxxxxxxxxx
server port:i:xxxxxx
domain:s:xxxxxxxxxxxxxxx

================================================== ================

Is it possible that the content-disposition being Attachment instead of 'inline' what is throwing it?

Thanks,
Ken

0 Kudos