I have an an app which is in testing, which we use PhoneGap to build the IOS and Android versions. I can only go back to version 6012, but have tested 6012, 6315 and 6348. They all have the same problem. The app has a UX login component (custom) which connects to a bound UX which then populates the user security data for editing by the user. You can test this yourself using the prebuilt ux components that Alpha gives you. This typical setup has worked fine until I did upgrades to Alpha at the end of last year (so, no problem with 5447 that I recall). The app works fine for IOS and Web (user data is loaded and can be edited as normal) but on Android no user data is loaded (and therefore can't be edited). Android does recognize the user and allows for login (and also denies if incorrect), so the base security system is recognized to some level. It just doesn't pass the user into the bound UX. No errors are returned at all.
I tried all the various PhoneGap settings (and different versions) I could think of to no avail. Since it works on IOS and the Web, I'm assuming that it's specific to Android and PhoneGap. I have a way of getting around this by not using a bound UX and using a list and then passing in the user. However, this isn't the way I want it to work, and it shouldn't have to be done that way, and it will create more work - so I don't want to do it.
I've tried the various methods of grabing the username and they just don't get passed on to the bound ux. They do pass on the username to, say, a field on the form. It's very odd to me.
Anyone seen this issue? I searched but couldn't find anything similar. We have several apps designed this way, all working, but they haven't been updated recently.
I tried all the various PhoneGap settings (and different versions) I could think of to no avail. Since it works on IOS and the Web, I'm assuming that it's specific to Android and PhoneGap. I have a way of getting around this by not using a bound UX and using a list and then passing in the user. However, this isn't the way I want it to work, and it shouldn't have to be done that way, and it will create more work - so I don't want to do it.
I've tried the various methods of grabing the username and they just don't get passed on to the bound ux. They do pass on the username to, say, a field on the form. It's very odd to me.
Anyone seen this issue? I searched but couldn't find anything similar. We have several apps designed this way, all working, but they haven't been updated recently.
Comment