You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just tried to migrate to the new offscreen rendering API with ImageScreenObject.
In some cases, the image is set correctly, but in others, the application crashes on draw.
AssetScreenObject seems to be also concerned with native video taken with the phone.
To Reproduce
Use ImageScreenObjet with PNG from assets :
if let image =UIImage(named:"test")?.cgImage {
imageScreenObject.verticalAlignment =.middle
imageScreenObject.layoutMargin =.init(top:0, left:0, bottom:16, right:0)
imageScreenObject.cgImage = image
}else{Logs.info("no image")}
With this image (just a screenshot) :
Result to :
Expected behavior
Integrate all kinds of PNG
Version
v1.9.1
xCode 15.4
Smartphone info.
No response
Additional context
No response
Screenshots
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered:
I have a hypothesis that crashes occur when the composite range of the PNG exceeds the screen size. To fix the issue, I need the following information:
Please provide a reproducible PNG file that causes the issue.
It's not good to crush, so I think it's better to either issue a warning or have the framework handle the clipping. For now, please avoid the issue using the above method. I will try to fix. Reopen.
Describe the bug
Hello,
I just tried to migrate to the new offscreen rendering API with ImageScreenObject.
In some cases, the image is set correctly, but in others, the application crashes on draw.
AssetScreenObject seems to be also concerned with native video taken with the phone.
To Reproduce
Use ImageScreenObjet with PNG from assets :
With this image (just a screenshot) :
Result to :
Expected behavior
Integrate all kinds of PNG
Version
v1.9.1
xCode 15.4
Smartphone info.
No response
Additional context
No response
Screenshots
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: