Hi,
I configured the view in the Perspective Designer, configured the Authentification Levels/Users and tried to open this view from the Chrome browser, Internet Explorer and Mobile application. In Chrome I had a success: logged in and got the view. In Internet Explorer I got a blank page… In the Moblile App I could log in, but got a message: View not Found. No view configured for this page.
1 Like
Internet Explorer is not supported. Perspective is written to target ‘modern’ browsers. Most of our testing includes Safari, Firefox, Chrome, Edge, but most current browsers should work as long as they support emcascript to approximately 2016/17 standards with support for CSS Grid, Async-Await, Flexbox. We’ll have firm version requirements for the different browsers we intended to support as we approach final release.
The view not found in the mobile app seems suspicious to me, I don’t think I’ve seen a case where something loads in chrome but the same view/route can’t be found in the app. Can you report back on the versions you’re testing, and provide some more info on the app configuration?
Have you got any ideas?
Two thoughts:
First: When you hit the back button it should show you a “settings” wheel, that is where I had to specify my Server. From there you can also specify the default “auto-launch” app.
Secondly: Make sure your page configuration is set properly on the page configuration tab (the “settings” gear on your lower left of the designer.)
This section(s) of the documentation was also very helpful.
https://docs.inductiveautomation.com/display/DOC80/Perspective+Sessions
https://docs.inductiveautomation.com/display/DOC80/Pages+in+Perspective#PagesinPerspective-PageURLs
(aka you need to make sure your primary view is set to what loads first)
I can’t find the way how to set up one of my views to startup default view. I made some test pages and views and i can switch over them via menu and links i have made, but still i can’t find the way, how to set up the first view, when the app loads.
I can see configured views on IOS devices but i have an error message on android phone, when trying to log in to the server.
Can you screenshot your view/page configurations?
Also, believe we have an bug report for some users using unicode characters in the page configuration paths. Are you using any non-english characters in your view names or paths? Looks like that might be the case and if so, you’re probably hitting a bug that we need to fix.
If you’d like to email or post a minimal project export (not a gw backup) of the perspective resources that reproduce the issue you’re seeing I’d be happy to take a look.
Perspective expects your landing or “main” page to always have a url of /. If you would like the “Main” View to be your project’s landing page, then change its URL to simply be /. There is no need for URLs to match View names (although I totally understand that it makes keeping track of everything a bit easier).
Please see the Docs.
The Documentation does say “typically”, which should probably be replaced with “always” - unless someone knows something I don’t.
1 Like
I am seeing the “view not found” on my perspective project after the latest build (downloaded today).
I did check to make sure my page URL is set to only /
And my primary view is set correctly.
Running on win10
iOS on iPod touch 6th gen, 12.1.1
1 Like
As a followup - we believe this was caused by an issue in how we handle unicode in perspective urls and are testing a fix. Keep an eye on changelogs, should make it into a nightly in the coming days.
Update: My problem went away with the new build
I believe your problem was caused by an incomplete fix for @andrei.plotnikov 's problem. Nearing a fix for his issue as well, but we’re taking extra time to test and validate to avoid re-introducing an issue like you encountered. Hopefully have it out this week though!
Interesting, that on android devices after log in, the app routes me to the browser and open there perspective view. On the IOS devices the view opens inside the app.
Thanks guys. I was having this problem too but hadn’t nailed it down enough to rule out my own error.