Johannes la Poutre
asked this on June 20, 2011 12:16
Client 5.0.3
Activating a layar intent from Safari on IOS does not always pass extra parameters, like this:
layar://mylayer?action=refresh&myParam=123
These intents do work correctly from the internal Layar web view
Comments latest first
Thanks. What about Layar Player?
Hello All,
The bug reported by Howard regarding the layar intent not working correctly in list view & map view is fixed in iPhone v6.0.
The one reported by Johannes(QAREV-193) is still open. I will remind the product team about it.
Best Regards,
Xuan
I have reported a very related issue with clear steps: http://devsupport.layar.com/entries/20333832-refresh-removes-request-parameters-and-returns-0-pois
Hello Howard,
Thanks! The issues are reproduced. Reporting them now.
Best Regards,
Xuan
Hi Xuan,
Thanks for looking at this.
Could you test the layar in San Fransisco - 37.7749295, -122.4194155 and let me know your thoughts.
Kind regards,
Howard
Hi Howard,
Thanks for letting us know. I have tested the issues (using a test layer) you mentioned using latest internal iPhone build and android v5.0.3. However, I could not reproduce the issues. I could not find POIs in your "myjobs" layer, can you provide us some test coordinates ?
Thanks
Xuan
I've got a problem with the layar:// intent too on iPhone v5.x.
I have an action like this:
The behaviour on Android is that it refreshes the layer, removes the POI and reloads a new set according to the parameters. Unfortunately, on iPhone, the original POI remain AS WELL as loading the new set. v 4.x of the iPhone client behaved as expected in AR view.
Another strange behaviour is that the layar:// intent refreshes the map view in Android but NOT list view. It doesn''t work at all for iPhone
Please check the layar called JobAmp to test it. http://m.layar.com/open/myjobs
Thanks
H
Hello Johannes,
Actually, we do not recommend to use Layar:// intent from outside of layar app. This is because you do not always know whether the user already has layar installed. It is better to use http://m.layar.com/open/<layername> in this scenario.
I have reported this issue QAREV-193.
Best regards,
Xuan