Please do ask about the VerifyAsync, because it doesn't make sense to us until explained.

The scenario is simple... a user has already logged in to mobile before, which gave him/her access to resources from the server via the web api. However, his/her account has been modified by an administrator from a user management module on a different application (e.g. a Desktop App), which connects to the same database. And since the user account had been modified (e.g. changed username/password), the account stored in a mobile device should no longer be valid.

Well, that's true... the account is no longer valid and the web api is smart enough to deny access to the user account, which is trying to access data using an outdated credentials from a mobile device. But our concern is the ability of the Crosslight framework to respond to these kind of scenarios. Simple enough that it should require the user to re-login from the mobile device, instead of showing the "Authorization has been denied for this request." error message everytime the app tries to access data from the server. And besides, the account should be validated when the app starts, even when the user account is already stored in the device. Ah! Yes, we believe it does execute the VerifyAsync method at startup, but always returns true for unknown reasons.

Hi,

Any updates on CROS-794 and CROS-795?

Thanks!

In relation to this concern, how can we implement the same behavior on other platforms like Android, WinPhone, etc? Are there equivalent objects on other platforms in relation to how the SetDetailViewController was used with iOS?

Okay, when would that be released?

Hi,

We understand that the Drawer is safe and we currently use that with an Advance Master/Detail view, since this was one of the available business templates when we started the project. However, most users don't want an extra menu click to get into another view. Or go back to the very start of the navigation history just to reach the hamburger menu. And clicking the menu, plus the animation delay causes productivity and is becoming an issue that we need to address. MultiPage or Tabbed navigation seems like a suitable solution to this issue, which we believe should be supported on all platforms, regardless of device type. However, if you're saying that a combination of these views is not possible... then we need to resort to something else, without using the drawer navigation.

The Advanced Master/Detail view is a crucial part of our business app, but we also need easier navigation without extra clicks and delays. The start and end time are recorded while using the app, which gives the clients ability to determine how much time a field operator was able to collect information. With added delays and few extra clicks... the productivity is affected. That being said, we welcome a better solution or workaround.