NoAccessSignal Exception thrown when trying to “Load More” in Mobile Controls view

Question

I have an XPages app running on 8.5.3 UP1 with a mobile controls interface. It works fine on my dev and test servers, but in production we\'re seeing the following intermittent

Answer 1

Keith and I have both encountered this behavior (in different applications) in the following scenario:

1. The current user was authenticated via Directory Assistance; in other words, they don't have an account in the primary Domino Directory.
2. The XPage has a page-specific ACL

For example, I used to use page ACL's in watrCoolr to specify that authenticated users would have editor access to the chat data source but anonymous would only have reader. That worked fine as long as I authenticated as a user explicitly registered in names.nsf. If I authenticated as a user defined in an LDAP directory, the page would stack trace. As soon as I switched to simply hiding editable controls from anonymous users and removed the page ACL, no more stack trace.

This might explain why it works fine in dev and test but blows up in production, if you're not using Directory Assistance in the former and they are in the latter.

Answer 2

OK this turned out to be a very odd issue which affected iOS devices specifically. I had written some extra code to detect if the app was running in standalone mode (ie that the user had created a shortcut to the app on the home screen). This code loops through all tags that have an onclick event and stops them from launching Safari and forces them to run inside the standalone browser window. In the case of the load more button this is what was causing the error on the server. I still don't understand why that was an error, but it was an easy fix, simply don't process the Load More button when I loop through everything else in the page.

Thanks for all the help everyone.