According to Crashlytics, this issue only on iOS 12, I can't to reproduce that.
There is an assumption that this is due to the toolbar for the keyboard, but what exactly the problem is is not clear.
Attempting to attach a window (<UITextEffectsWindow: 0x1380bfa00; frame = (0 0; 320 480); hidden = YES; layer = <UIWindowLayer: 0x2830cc5e0>>) to a screen with a nil FBSDisplayIdentity
Related
I am using JSQMessageViewController and I am facing the issue (only in ios14) that i cant see media items like Images, Video and Audio in device though these views are generating debug view hierarchy. See below attached image:-
debug view hierarchy screenshot:
here is the description of UIImage inside collection view cell:
<UIImageView: 0x7fe7d6d95b30; frame = (20 8; 177 131); clipsToBounds = YES; opaque = NO; autoresize = RM+BM; userInteractionEnabled = NO; layer = <CALayer: 0x600001ce4ec0>>
here is the screenshot attached of screen:
You can see the view has generated space for image, but its not showing up!
Is anyone facing this issue? how can i solve this problem. This issue is occurring in iOS 14, it works perfectly in iOS 13.
You need to overwrite in JSQMessagesMediaViewBubbleImageMasker.m
method - (void)jsq_maskView:(UIView *)view withImage:(UIImage *)image and change line:
view.layer.mask = imageViewMask.layer;
to be
view.maskView = imageViewMask;
I suggest you to use category for that. For me that was solution.
I would like to suggest to change like as follows along with the Vladimir answer for backward compatibility:
if (#available(iOS 14.0, *)) {
view.maskView = imageViewMask;
} else {
view.layer.mask = imageViewMask.layer;
}
I found this good link how to get selected images.
I am trying to set image that I get from extension context to image view that I placed in storyboard.
this my print out code po self.theImageView:
<UIImageView: 0x7b8a1c90; frame = (240 89; 52 41); opaque = NO; autoresize = RM+BM; userInteractionEnabled = NO; layer = <CALayer: 0x7b887fa0>> - (null)
and this is po self.theImageView.image
<UIImage: 0x7a6977f0>
So I even can see image using eye tool when debug it:
But on the screen of my simulator there is no visible image.
I am a xamarin developer, I am using visual studio xamarin and using a virtual MAC machine in my windows machine for build and deployment. Today I have updated the Xamarin to Xamarin 3.
Now I am facing an issue.
I am able connect Xamarin iOS Build Host.
But the issue is, when I try to run the application, I am getting “deployment errors” message.
Error description is as follows.
1>Build server returned an Error.
1>2014-05-29 15:12:31.338 Interface Builder Cocoa Touch Tool[367:303]
1>WARNING:
1>Reason: Could not find layout engine view for view's (<UILabel: 0x18ec1b90; frame = (5 0; 20 20); text = '31'; clipsToBounds = YES; opaque = NO; autoresize = RM+BM; userInteractionEnabled = NO; layer = <CALayer: 0x18eafcd0>>) coordinate space view <UIView: 0xb6515a0; frame = (0 0; 50 65); autoresize = W+H; gestureRecognizers = <NSArray: 0x18ee7ca0>; layer = <CALayer: 0x18ec9cd0>>. But the canvas coordinateSpaceView is view's superview, so we are assuming the same in the layout engine.
1>File: /SourceCache/IBAutolayoutFoundationIOS/IBAutolayoutFoundation-3430/Framework/Classes/Arbitration/IBAutolayoutEngine.m:335
1>Method: -[IBAutolayoutEngine layoutFrameForView:inCoordinateSpaceOfView:]
Please let me know ,if you have any idea regarding this issue..
I've got this weird issue with my iOS app where a stuck pixel often appears after a while using the application and I can't find where it came from.
I've even done the following with LLDB and it is still there:
expr [((UIWindow *)((UIApplication *)[UIApplication sharedApplication]).keyWindow) setHidden:YES] // and removeFromSuperview
The pixel disappears when you close the app and reappears when you open it again.
Any ideas on how I can debug this further? Unfortunately I haven't managed to reproduce it consistently.
EDIT: this managed to remove the pixel:
[(UIWindow *)[(NSArray *)((UIApplication *)[UIApplication sharedApplication]).windows objectAtIndex:2] setHidden:YES]
The objectAtIndex 2 was:
<UITextEffectsWindow: 0x14de6280; frame = (0 0; 768 1024); gestureRecognizers = <NSArray: 0x14dd77a0>; layer = <UIWindowLayer: 0x14deb7f0>>
Any ideas?
EDIT: narrowed it down more. The pixel was removed while debugging by doing this:
expr [((UITextMagnifierCaret *)[(NSArray *)((UIWindow *)[(NSArray *)((UIApplication *)[UIApplication sharedApplication]).windows objectAtIndex:2]).subviews objectAtIndex:0]) remove]
I'm running into a tricky glitch.
I've got a .xib, which was created by XCode when I created a new UIViewController subclass. It has quite a few elements, including some UIButtons, a bunch of UILabels, a small UIView with some other views inside it, and a UIImageView containing a mostly-transparent image.
In viewDidLoad, I set the background color of the UIImageView to a color using a pattern image.
When I display this view controller in the simulator or on my iPhone 4 (both running iOS 5.1), everything goes smoothly; the patterned background displays, all the interactions work, and so on.
When I test on iOS 4.3, however (either in the simulator or on my iPod Touch 2G), it appears that everything I'm trying to manipulate based on an outlet (e.g. [self.myBackgroundImageView setBackgroundColor...] or [self.mySegmentedControl setEnabled:NO]) just doesn't work at all.
The only even vaguely unusual thing I'm doing when the view gets presented is this, which makes it size properly in a popover:
- (void) viewWillAppear:(BOOL)animated {
CGSize size = CGSizeMake(320, 480); // size of view in popover
self.contentSizeForViewInPopover = size;
[super viewWillAppear:animated];
}
I really can't think of anything else that might be the problem. I've cleaned, rebuilt, all that stuff. Still no dice.
Has anyone else encountered this?
UPDATE per request by ott:
Added the following at the end of -viewDidLoad:
NSLog(#"self.myBackgroundImageView = %# | %#", [self.myBackgroundImageView description], [[self.myBackgroundImageView backgroundColor] description]);
...The output is:
self.myBackgroundImageView = <UIImageView: 0x6d48c80; frame = (0 0; 320 480); autoresize = RM+BM; userInteractionEnabled = NO; layer = <CALayer: 0x6d48b60>> | <UIImageView: 0x5f459b0; frame = (0 0; 320 480); autoresize = RM+BM; userInteractionEnabled = NO; layer = <CALayer: 0x5f45890>> // kCGColorSpaceModelPattern 1
So... not nil. Not sure what the story is here.
UPDATE 2:
It appears the disabling of a UISegmentedControl in iOS 4.3 doesn't dim its display, so that's what that part was about. As for the background pattern image: I can't find confirmation of this, but I'm starting to think it's a bug in iOS 4 that makes a background color using a pattern-image UIColor not display properly on a UIImageView. It works fine if I make the UIImageView have a clear background and put the pattern image UIColor as the background of the main view instead. If anyone comes up with a workaround, or confirmation that this is indeed an iOS 4 bug, it would be much appreciated.