Obsolete
Status Update
No update yet.
Comments
dn...@google.com
Can you provide the below requested information to better understand the issue:
Can you please test with latest library and update result here.
https://developer.android.com/topic/libraries/support-library/revisions.html
If possible please provide a complete sample application.
Expected output
What do you expect to occur?
Current output
What do you see instead?
Can you please test with latest library and update result here.
If possible please provide a complete sample application.
Expected output
What do you expect to occur?
Current output
What do you see instead?
ok...@gmail.com
This seems to be intended according to https://issuetracker.google.com/74278849 , the suggestion is to remove the extra logic to deliverResult() in onStartLoading().
ku...@google.com
@gg..@google.com
Sample project is attached.
Steps to test:
1. Import, build and install apk
2. Notice "Number of 'onLoadFinished' calls: 1"
3. Click "Click me!" button to start Second Activity
4. Notice "Number of 'onLoadFinished' calls: 2"
EXPECTED: At stap 4 "Number of 'onLoadFinished' calls" should be 1.
ACTUAL: It's 2.
@ha...@gmail.com
That's not the solution because developers are not in control of all Loaders. For example CursorLoader from support libaray should be then fixed by google, not by developers.
And this is behavior change which is not documented, so suggestion on issuetracker is not good enough.
Sample project is attached.
Steps to test:
1. Import, build and install apk
2. Notice "Number of 'onLoadFinished' calls: 1"
3. Click "Click me!" button to start Second Activity
4. Notice "Number of 'onLoadFinished' calls: 2"
EXPECTED: At stap 4 "Number of 'onLoadFinished' calls" should be 1.
ACTUAL: It's 2.
@ha...@gmail.com
That's not the solution because developers are not in control of all Loaders. For example CursorLoader from support libaray should be then fixed by google, not by developers.
And this is behavior change which is not documented, so suggestion on issuetracker is not good enough.
ok...@gmail.com
We have shared this with our engineering team and will update this issue with more information as it becomes available.
dn...@google.com
Do you have any news ?
ok...@gmail.com
@6 I think they changed the way it works, without much information about the change.
Try this solution I've written about (read the last part of the text too, as it talks about the changes) :
https://stackoverflow.com/a/22675607/878126
Try this solution I've written about (read the last part of the text too, as it talks about the changes) :
dn...@google.com
@7 Thank you for your information. I still get the error when orientation change
ok...@gmail.com
@8 I can't confirm. It works fine without any error .
Attached sample project, that "loads" content, and after 5 seconds returns a result, that will be returned on the current Activity.
Attached sample project, that "loads" content, and after 5 seconds returns a result, that will be returned on the current Activity.
dn...@google.com
OK I'll check it again. Thx a lot!
ro...@gmail.com
@9 Hello man, when orientation change the "onLoaderFinished" method, called again. Do you know how to stop calling this method?
gm...@gmail.com
@11 It is called only once after onCreate is called, just as intended.
The reason is that after you load something, you wish to use it. After orientation change, all is destroyed, but the result is still available, so you can use it.
If you don't want to use the result, either ignore it, or check whether the loader (if existing) has a result or not.
But this loses the whole point of using a loader. By using a loader, you are supposed to use its result, even after an orientation change.
The reason is that after you load something, you wish to use it. After orientation change, all is destroyed, but the result is still available, so you can use it.
If you don't want to use the result, either ignore it, or check whether the loader (if existing) has a result or not.
But this loses the whole point of using a loader. By using a loader, you are supposed to use its result, even after an orientation change.
ch...@gmail.com
I have the same problem。It used in v25,but not in v26 and v27
ko...@gmail.com
I have the same problem - com.android.support 27.1.1. When NestedScrollView is scrolled by user then call smoothScrollTo isn't accurate.
[Deleted User] <[Deleted User]>
Same problem. Works on support lib 25 but fails on 27.
is...@google.com
vi...@google.com
[Deleted User] <[Deleted User]>
I encountered the same issue, if Recycler view is nested inside a Nested Scroll View. Call to NestedScrollView.smoothScrollTo(x, y) does not work correctly.
Description
Version used: 27.0.2
Theme used:Theme.AppCompat.Light.NoActionBar
Devices/Android versions reproduced on: api 24 (Xiaomi mi4c)
After update support library (25.4.0 -> 27.0.2) NestedScrollView smoothScrollTo() doesn't work. In 25.4.0 this method work well.
<RelativeLayout
android:layout_width="match_parent"
android:layout_height="match_parent"
android:orientation="vertical">
//-----//
<android.support.v4.widget.NestedScrollView
android:layout_width="match_parent"
android:layout_height="wrap_content">
<android.support.v7.widget.RecyclerView
android:nestedScrollingEnabled="false"
android:layout_width="match_parent"
android:layout_height="wrap_content"/>
</android.support.v4.widget.NestedScrollView>
//-----//
</RelativeLayout>