You need to sign in to do that
Don't have an account?

Angular SPA app routing not working properly in a Visual Force page
I have created a SPA app using javascript with the Angular framework. The app works fine in Classic, but the routing does not work properly in Lightning. The page loads fine, but when navigating to another page within the app it opens another window and give the following message "You don't have access to this record. Ask your administrator for help or to request access."
If you close that message the following message appears
"This list view isn't available in Lightning Experience. To see this list view, use Salesforce Classic or switch to another list view." Sometimes it will open a new tab or window with the following:
URL No Longer Exists
You have attempted to reach a URL that no longer exists on salesforce.com.
You may have reached this page after clicking on a direct link into the application. This direct link might be:
• A bookmark to a particular page, such as a report or view
• A link to a particular page in the Custom Links section of your Home Tab, or a Custom Link
• A link to a particular page in your email templates
If you reached this page through a bookmark, you are probably trying to access something that has moved. Please update your bookmark.
If you reached this page through any of the other direct links listed above, please notify your administrator to update the link.
If you reached this page through a link on our site, please report the broken link directly to our Support Team and we will fix it promptly. Please indicate the page you were on when you clicked the link as well as any other related information. We apologize for the inconvenience.
Thank you again for your patience and assistance. And thanks for using salesforce.com!
The strange thing is that if you go back to original window with the SPA app, it will display the correct page and everything works fine. If you navigate to a new page in the SPA app the scenario start all over again.
If you close that message the following message appears
"This list view isn't available in Lightning Experience. To see this list view, use Salesforce Classic or switch to another list view." Sometimes it will open a new tab or window with the following:
URL No Longer Exists
You have attempted to reach a URL that no longer exists on salesforce.com.
You may have reached this page after clicking on a direct link into the application. This direct link might be:
• A bookmark to a particular page, such as a report or view
• A link to a particular page in the Custom Links section of your Home Tab, or a Custom Link
• A link to a particular page in your email templates
If you reached this page through a bookmark, you are probably trying to access something that has moved. Please update your bookmark.
If you reached this page through any of the other direct links listed above, please notify your administrator to update the link.
If you reached this page through a link on our site, please report the broken link directly to our Support Team and we will fix it promptly. Please indicate the page you were on when you clicked the link as well as any other related information. We apologize for the inconvenience.
Thank you again for your patience and assistance. And thanks for using salesforce.com!
The strange thing is that if you go back to original window with the SPA app, it will display the correct page and everything works fine. If you navigate to a new page in the SPA app the scenario start all over again.
imports: [RouterModule.forRoot(routes, { useHash: true })],
This solved the above problem, but now the screen becomes unstable when changing routes.
All Answers
List views display and behave differently in Lightning Experience.
Kanban View
For further reference, you can check this,
https://salesforce.stackexchange.com/questions/45552/visualforce-angular-js-ui-router-not-working
Let me know if it helps you and close your query by marking it as solved so that it can help others in the future.
Thanks.
imports: [RouterModule.forRoot(routes, { useHash: true })],
This solved the above problem, but now the screen becomes unstable when changing routes.
For addtional information on previous response.