63
Views
8
Comments
[Pin Code] Pincode haspin error
Question
Forge component by Labs
10
Published on 23 Apr 2018

The haspin action always returns true since it calls GetValue and checks whether it is empty or not. Though it returns "false" instead of nothing when it can't find a value.


mvp_badge
MVP
Rank: #160

Hi Frank,

The plugin has an action to do that.

mvp_badge
MVP
Rank: #160

Do you have the latest version and did you checked the Sample Flow to see how to implement!

There are some details that you need to be aware, like if the user is logged in.

mvp_badge
MVP
Rank: #160

Well, I think I can't help you more without more detail, recently my team made several applications where the PinCode was implemented and it's working fine in all of them.

A few last points you can try, does this happen in all devices, did you try to uninstall the application and install it again. 

Please note that when you add a new plugin a new version of the app needs to be generated.

Staff
Rank: #201

Hello Frank,

If I'm understanding correctly, the problem may be with the value that is returned from the KeyStorePlugin.

Which version of the Key Store Plugin do you have installed?

Also, are you testing this specific feature on a real device or via your browser? 

Cheers,

Samuel Jesus

Rank: #1761

Hi Samual,

I'm testing it on an android device with the latest version of the Key Store Plugin.

We changed the comparison (as shown in the screenshot in the original post) to GetValue..Value <> "False"  and it works like a charm again.


It did use to work before; thats why I think the output of the Key Store Plugin changed from empty to "Failed".


For now I can work with it. I mainly wanted to address this point to the lab team via this way.


Nevertheless thanks a lot for your effort (and Nuno too!).

Staff
Rank: #201

Hello Frank,

That is my suspicion as well.

The Pincode component was done using a previous version of the Key Store plugin.

The newer version of the plugin may have altered the mechanism.

I'll share this feedback with the team, but for now, I'm glad to hear you found a workaround for your app :)

Cheers,

Samuel