[AC-5673] Android: Nested ScrollViews are not working for Titanium SDK 6.3+
| GitHub Issue | n/a |
|---|
| Type | Bug |
|---|
| Priority | n/a |
|---|
| Status | Resolved |
|---|
| Resolution | Duplicate |
|---|
| Resolution Date | 2018-03-31T23:37:25.000+0000 |
|---|
| Affected Version/s | Appcelerator Studio 4.5.0 |
|---|
| Fix Version/s | n/a |
|---|
| Components | Titanium SDK & CLI |
|---|
| Labels | android |
|---|
| Reporter | Pritish Patil |
|---|
| Assignee | Shak Hossain |
|---|
| Created | 2018-03-24T06:20:38.000+0000 |
|---|
| Updated | 2018-03-31T23:37:25.000+0000 |
|---|
Description
I have horizontal ScrollView nested inside a vertical ScrollView which works fine on Ti SDK 6.2.2 but when I compile it using Ti SDK 6.3 and above the scroll for horizontal ScrollView doesn't work properly. Due this issue I am unable to upgrade Titanium SDK for my app.
Platform : Android
SDK : 6.3+
System details
Operating System
Name = Mac OS X
Version = 10.12.6
Architecture = 64bit
# CPUs = 4
Memory = 4294967296
Node.js
Node.js Version = 8.9.3
npm Version = 5.5.1
Titanium CLI
CLI Version = 5.0.14
Titanium SDK
SDK Version = 7.0.1.GA
Target Platform = android
Attachments
| File | Date | Size |
|---|
| app.js | 2018-03-24T06:19:51.000+0000 | 4897 |
Hello, I tried to test the issue with SDK 7.1.0GA and in SDK 6.2.2.GA. I am not sure what seems to be the issue here? I get the same outlook in the emulator for both SDK. Can you explain a bit more on this? Thanks.
This was likely fixed in 7.1.0 as parr of TIMOB-25552, please confirm.
Hi, I compiled the project using SDK 7.1.0 but still have the problem with horizontal scrollview added at the bottom of the vertical scrollview. When I scroll the horizontal scroll, the vertical one also automatically moves up and down which I don't want. The same code works fine on SDK 6.2.2. Tested on OnePlus 2 (Android 6.0.1) Output on 6.2.2 : https://goo.gl/fsD5hB Output on 7.1 : [https://goo.gl/L4tioT] Scroll works fine till 6.2.2 but after that it does not.
This is still an open issue: [TIMOB-25792] [~ppatil], the above ticket has a work-around you can use too.