Community
Participate
Working Groups
Created attachment 244556 [details] Test results for Click in components - execution error
Click in component action for iOS Button causes Execution Error: "*** -[__NSPlaceholderDictionary initWithObjects:forKeys:count:]: attempt to insert nil object from objects[0]" Test results are attached.
Since this is a bug which is from a current sprint task i raise the importance to P1
Actually I can not reproduce this error. I need more information for this. With which component did you try it? You always can reproduce this error or just sometimes? Basically this error comes when we try to add a nil value to NSDictionary or NSArray. I just have to figure out where it is happened.
I´ve got it for clicking on the Button on the main page with label "Buttons" for old aut (with "iPhoneMainStoryboard" storyboard). For new aut ("iPhone" storyboard) I got for the same components Execution Error: "+[NSInvocation _invocationWithMethodSignature:frame:]: method signature argument cannot be nil"
We figure out this problems comes only for buttons and the problem with the buttons is with object mapping. We easily can map the button label (UIButtonLabel) instead of UIButton.
The issue is that UIButton is a private thing so we cannot click it thought it is a graphical component. We can think if we should have a normal Label instead of UIButtonLabel for Buttons, because with private labels we cannot do any actions.
Created attachment 244601 [details] Successfull_click_on_Component_with_Text_Input For some mappable components are currently disabled for user interaction (tap, long tap, swipe) and we have on a try to do this Execution Error: "The step timed out after 10.00 seconds: View is not enabled for interaction": I´ve observed such behaviour for UIButtonLabel and when I map a textfield as a "Component with text" (tap) instead of mapping it as a "component with text input" (long tap). I think at least we should change somehow the error description for such cases, e.g. "Action error: this component cannot be tapped" or discuss what other behaviour is correct in this case.
Created attachment 244602 [details] Click on Textfield (component with text) fails with execution error Click on Textfield fails with execution error (not supported user interactions) when it is mapped as a component with text, thought click succeeds for Textfield when it is mapped as a component with text input.
Removed the error message ( as we talked with Mma ) when view is not enabled for user interaction. https://bitbucket.org/jubula/com.bredexsw.jubula.core/commits/507c2d207dbbca510491eb533e0f113fd36c8de5
I´ve tested, that the error is not occurring any more. Thus, this can be closed as resolved.
Setting this to resolved because of comment 9 and closing this ticket because of comment 10
