Posts

Post not yet marked as solved
20 Replies
Same problem and now they've removed the option to run the Simulator under Rosetta which was the only fix. How can such a fundamental piece of the user experience still be broken on their architecture after a year and a major Xcode release? I'll guess I'm stuck with v13 for the foreseeable future.
Post not yet marked as solved
4 Replies
Just an FYI. I use to do this until one time I submitted an update and it was rejected for programmatically checking for updates. That was a number of years ago so policies may have changed and I haven't tried it since to find out.
Post not yet marked as solved
7 Replies
I'm having the same issue. Assuming I needed to agree to a new document of some type I went Agreements, Tax and Banking and it won't load. I assume they're related issues.
Post not yet marked as solved
2 Replies
Same problem here. Also, when I try to add a new build it throws up an empty dialog with an Agree button. Clicking Agree dismisses the dialog but doesn't create a new build.
Post not yet marked as solved
6 Replies
I'm having the same issue, I submitted an update 15 hours ago and haven't received a single notification or email. It's never been a problem in the past and I assume it's related to Apple springing the release of iOS14 on developers. KMT - if the back end can't handle the load Apple shouldn't announce they're releasing a new OS without warning.
Post marked as solved
7 Replies
As mentioned in the stack overflow posting in iOS 13 sliding your finger across a segmented control selects segments. I assume you're running 13 so I'm not sure why you're not seeing it.
Post marked as solved
7 Replies
Turns out the issue isn't with the scroll view but with the segmented control. In iOS 13 you can swipe/pan to change the selected segment which prevents the scroll view from scrolling. The solution is to subclass the control, override gestureRecognizerShouldBegin and paradoxically return true.class NoSwipeSegmentedControl: UISegmentedControl { override func gestureRecognizerShouldBegin(_ gestureRecognizer: UIGestureRecognizer) -> Bool { return true } }Here's a link to the relevant posting on stack overflow: https://stackoverflow.com/questions/58177165/ios-13-segmented-control-remove-swipe-gesture-to-select-segment
Post marked as solved
7 Replies
It's actually Objective-C - this code's been around for awhile - and as I pointed out this works fine for every version of iOS up to 13. Here's the relevent set-up code: NSInteger numSegs=typeControl.numberOfSegments-2; CGFloat offset=[self eventTypeScrollViewOffset]; typeControl.frame=CGRectMake(0, 0, (kEventTypeScrollPadding*2)+(kEventTypeSegmentWidth*numSegs), typeScrollView.frame.size.height); typeScrollView.contentInset = UIEdgeInsetsMake(0, -offset, 0, offset); typeScrollView.scrollEnabled=YES; typeScrollView.contentSize=CGSizeMake(typeControl.frame.size.width-(offset*2),typeScrollView.frame.size.height);and here's the output from the debugger after the scroll view has been set-up:<UIScrollView: 0x7f93ba0d2600; frame = (0 0; 375 30); clipsToBounds = YES; autoresize = W+BM; gestureRecognizers = <NSArray: 0x600002f90360>; layer = <CALayer: 0x6000020fb880>; contentOffset: {188, 0}; contentSize: {1125, 30}; adjustedContentInset: {0, -187.5, 0, 187.5}>As you can see the contentSize is set and larger then the frame.Here's a link to screenshot that show's the actual implementation: https://i.stack.imgur.com/Fmpou.png
Post marked as solved
7 Replies
Thanks for the response. The scroll view's content is the control and the width of the control is wider then the device's screen. For instance the control has 8 segments but the screen is only wide enough to display 3 at a time. To see the other segments the user scrolls the view left or right. I can scroll the view progammatically but it doesn't scroll via user touches.(I included a picture but it doesn't display)