The event listener attached to the scroll view returns nil when printing event.phase.
event.limitReached and event.direction seem to work fine.
the issue is also present in the example in the API docs
I posted this issue on github, is this a known issue soon to be resolved?
Thanks Bram
Seems like this issue is still there in the most recent G2 release (ie #2076) as well.
I’ve experienced the same behavior and filed it as a bug yesterday afternoon (Case 28117) before seeing this post. No response from Corona yet.
There hasn’t been a daily build since November 13, so it hasn’t been fixed yet.
I just noticed there’s a discussion of the same bug here as well:
http://forums.coronalabs.com/topic/41531-eventphase-not-detected-in-scrolllistener-of-scrollview/
FYI, there’s Yet Another Thread (this one is in the daily builds section) noting this bug as well:
http://forums.coronalabs.com/topic/41361-daily-build-1260-broke-scrollview-listeners/
The more buzz we make the higher it will be on their priority list (i hope) 
any reaction on the bug report?
Bram
Alas, I haven’t received a response to my bug report yesterday re: scrollview event.phase, which I’ve also mentioned in an aside in email to Walter (he had asked me via email for more detail regarding an unrelated webview bug).
There’s another bug filed around the same time as mine on the same topic, according to the daily build thread. That bug is Case 28111.
I suppose I could regress to an earlier daily build – maybe pre-1260 – but there seems to have been a reasonable amount of surgery performed on the scrollview for build 1260 and I’d rather only have to work on this part of the code once and then leave it alone.
Good to hear!
Is there an estimate on when the fix wil be implemented?
Thanks,
Bram
Thanks, Brent. Though a more precise estimate on the fix time would, as Bram said, be useful. The latest release came out approximately a week ago, and bug reports on this problem were filed days ago.
Can you give us a hint? Will it be this week?
Hi all, it should be this week, but it’s sort of “out of my hands” at this stage. I believe it’s being tested a.t.m.
Thanks,
Brent
So daily build 2013.2082 came out today, and there’s no mention of the scrollview bug being fixed:
http://developer.coronalabs.com/release/2013/2082/
I’m monitoring this, and it appears that it’ll come in the next release (not 2082, but next one after that). Thanks for your patience everybody.
Brent
I presume for the rest of us who don’t have access to daily builds we will be left stranded with a buggy G2.0 release then?
Ow snap! That is indeed a big issue,
wil the basic/starter users get a chance to work with a proper working G.2 release?
I’ve been informed that we’ll probably be releasing a new public build (2.0-based) with this and other fixes implemented. I don’t have an ETA on that yet, but it shouldn’t be too far off.
Best regards,
Brent
Ah that’s good news!
When there is a estimate, would you be so kind to let us know?
Thanks,
Bram
have the same issue. any idea when it would be fix and publish on public build.
it’s a inconveniencing !
thanks for response
Guillaume
Same huge problem here. I converted my projects on Graphics 2.0 usin the build #2076 but ScrollView became totally unusable. Hope it will be fixed really soon because my apps are down.
What’s the news from this eagerly awaited new public build?
thanks for response
Florent
Until Corona releases a new public build, you might want to try the open source version of Widgets 2.0, which is a few months old. Then you can add back the missing functionality and customize it the way you want. I ended up preferring that over the daily build.
(And I agree it’s a shame we have to have these discussions at all. By this point in an SDK’s maturity, a fast and feature-complete scrollview should be expected.)