Skip to content
New issue

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

发送的gif动图能在电脑端正常显示,但无法在手机端打开 #1543

Closed
Numendacil opened this issue Sep 11, 2021 · 1 comment · Fixed by #1548
Closed

发送的gif动图能在电脑端正常显示,但无法在手机端打开 #1543

Numendacil opened this issue Sep 11, 2021 · 1 comment · Fixed by #1548
Labels
M 优先级: 主要 t:problem 类型: 不容易归类为特性或 bug 的综合问题 x:protocol 属性: 协议相关
Milestone

Comments

@Numendacil
Copy link
Contributor

更新mirai-core/mirai-console后使用机器人发送的动图无法在手机端显示(图片静止且点开后为空白),但在电脑端(以及iPad)可以正常播放。直接在官方客户端发送该动图则显示正常(已使用多组动图测试过,所以应该不是图本身的问题)

2021-09-11 10:22:27 V/Bot.1095860327: Event: Succeed(target=Group(758178836), source=net.mamoe.mirai.internal.utils.ExternalResourceImplByFile@272d64bf, image=[mirai:image:{6815FB94-C94B-D164-6F7B-6590775B19BF}.gif])                       
 2021-09-11 10:22:27 V/Bot.1095860327: Event: GroupMessagePreSendEvent(target=Group(758178836), message=[mirai:image:{6815FB94-C94B-D164-6F7B-6590775B19BF}.gif])                                                                                
2021-09-11 10:22:27 V/Bot.1095860327: Group(758178836) <- [mirai:image:{6815FB94-C94B-D164-6F7B-6590775B19BF}.gif]      
2021-09-11 10:22:27 V/Bot.1095860327: Event: GroupMessagePostSendEvent(target=Group(758178836), message=[mirai:image:{6815FB94-C94B-D164-6F7B-6590775B19BF}.gif], exception=null, receipt=net.mamoe.mirai.message.MessageReceipt@622fee3e)

复现

发送任意动图

版本及相关选项选择

  • mirai-core: 2.7.1-dev-1
  • bot-protocol: ANDROID_PHONE
  • mirai-api-http: 2.3.0

网络日志

2021-09-11 10:20:45 V/Net 1095860327: Send: MessageSvc.PbSendMsg(MessageSvc.PbSendMsg)
2021-09-11 10:20:45 V/Net 1095860327: Recv: MessageSvc.PbSendMsg
2021-09-11 10:22:27 V/Net 1095860327: Send: ImgStore.GroupPicUp(ImgStore.GroupPicUp)
2021-09-11 10:22:27 V/Net 1095860327: Send: MessageSvc.PbSendMsg(MessageSvc.PbSendMsg)
2021-09-11 10:22:27 V/Net 1095860327: Recv: ImgStore.GroupPicUp
2021-09-11 10:22:27 V/Net 1095860327: Recv: MessageSvc.PbSendMsg

补充信息

@Numendacil Numendacil added the x:question 标签: 需要更多信息 label Sep 11, 2021
@sandtechnology
Copy link
Collaborator

sandtechnology commented Sep 11, 2021

#1204

@Him188 Him188 added M 优先级: 主要 t:problem 类型: 不容易归类为特性或 bug 的综合问题 x:protocol 属性: 协议相关 and removed x:question 标签: 需要更多信息 labels Sep 11, 2021
@Him188 Him188 added this to the 2.8.0-M1 milestone Sep 11, 2021
Him188 pushed a commit that referenced this issue Sep 15, 2021
* Add height, width, size and imageType attribute to Image class
Close #1543 #1204 #1032

* Let ImageType enum code before the `Internals`, Also add @JvmStatic and OrNull version for match method

* Use runBIO and throws annotation for getImageInfo

* Add .kt suffix for MPP imagesImpl

* Return empty imageInfo for unsupported images

* Fix wrong file name

* apiDump

* Renaming MPP file instead of adding JvmName annotation

* Optimize readability and only use BIO at call-site

* Fix bug for detecting image type

* Detecting javax module for java 9+

* Clean up

* Disable some image types which not supported

* Use cross platform code to read images, readd support for apng

* Fix bug in reading image

* apiDump

* Fix bug in image reading and write unite test

* Fix wording

* Remove webp support and throws IllegalArgumentException for unsupported format

* Remove WEBP enum type

* Add unit test for unsupported image and correct comments

* Fix buffer input stream error when reading images

* Applying suggestions and fix jpg reading

* Add complete SOF decoding for jpg and clean up

* Caching jpg sof byte ranges

* Save `values()` as IMAGE_TYPE_ENUM_LIST for preventing clone operation

* Remove duplicated it
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
M 优先级: 主要 t:problem 类型: 不容易归类为特性或 bug 的综合问题 x:protocol 属性: 协议相关
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants