Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 438378

Summary:	wrong or private component when we map Objects in iOS
Product:	[Technology] Jubula	Reporter:	Kiss Tamás <tamas.kiss>
Component:	RC	Assignee:	Project Inbox <jubula.rc-inbox>
Status:	CLOSED WONTFIX	QA Contact:	Oliver Goetz <Oliver.Goetz>
Severity:	normal
Priority:	P3	CC:	alexandra.schladebeck, markus.tiede
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	iOS
Whiteboard:
Bug Depends on:
Bug Blocks:	437137, 438026

Description Kiss Tamás

2014-06-27 07:25:39 EDT

Sometimes we can reach private components with object mapping (for example UITabBarButton or UIButtonLabel). I think it is a problem, because the user usually not working with private APIs or at least we do not support Jailbreak devices and it makes harder to map the real component what we want (e.g. UIButton). I assume that, somehow we should avoid that in iOS object mapping.

Comment 1 Alexandra Schladebeck

2014-06-30 11:14:12 EDT

Thanks for the information Tamas. Can you say what steps we would need to take to change this and what the effects would be?

Comment 2 Kiss Tamás

2014-07-01 03:44:10 EDT

My opinion somehow check in iOS side the component is private or not. If it is private I will check the view below that also. If I reach a non private view I will send that back. With that mechanism the user always will get back the correct public view.

Comment 3 Markus Tiede

2015-01-12 08:48:38 EST

Re-assigning to default as assignee is no longer available.

Comment 4 Marvin Mueller

2016-05-31 09:08:44 EDT

We have dropped support for the iOS Toolkit