We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug UI display error after deleting photo. 照片从手机中删除后,app切换相册目录时UI显示错误。
How to reproduce Use the example from the project. 使用官方项目中的 example。
Steps to reproduce the behavior: case A: Screenshots 1 (如图1所示)
case B: Screenshots 2 (如图2所示) 1... 2... 3... 4. Delete all photo in 'A' path (删除目录A中的所有照片) 5. Switch to path 'A' (切换目录至A) 6. It's always loading (一直在加载中) 7. Can't switch path (不能切换目录)
Expected behavior like WeChat: Photos are still displayed after being deleted. 跟微信类型:照片从手机中删除后,app切换相册目录时,该照片仍然显示。
Screenshots
Version information
Additional context 1、猜测为切换目录时,更新目录下的资源导致。 2、微信中删除照片,仍然可以选择,并且可以正常发送。 3、建议跟微信类似,如果删除照片后,切换目录时更新资源,可能会导致其他UI显示错误: 当前页面的刷新问题、目录列表的刷新问题、选中状态的更新问题等。 4、安卓手机未测试。
The text was updated successfully, but these errors were encountered:
你使用的是自定义的 tab 示例,请切换至首页的示例再进行测试。
Sorry, something went wrong.
首页的 Image picker,效果是一样的。
No branches or pull requests
Describe the bug
UI display error after deleting photo.
照片从手机中删除后,app切换相册目录时UI显示错误。
How to reproduce
Use the example from the project.
使用官方项目中的 example。
Steps to reproduce the behavior:
case A: Screenshots 1 (如图1所示)
case B: Screenshots 2 (如图2所示)
1...
2...
3...
4. Delete all photo in 'A' path (删除目录A中的所有照片)
5. Switch to path 'A' (切换目录至A)
6. It's always loading (一直在加载中)
7. Can't switch path (不能切换目录)
Expected behavior
like WeChat: Photos are still displayed after being deleted.
跟微信类型:照片从手机中删除后,app切换相册目录时,该照片仍然显示。
Screenshots
Version information
Additional context
1、猜测为切换目录时,更新目录下的资源导致。
2、微信中删除照片,仍然可以选择,并且可以正常发送。
3、建议跟微信类似,如果删除照片后,切换目录时更新资源,可能会导致其他UI显示错误: 当前页面的刷新问题、目录列表的刷新问题、选中状态的更新问题等。
4、安卓手机未测试。
The text was updated successfully, but these errors were encountered: