I use `SwiftyStoreKit` to request In App Purchases and get only this error with iOS 13:

    Error: Optional(Error Domain=ASDErrorDomain Code=507 &quot;Error decoding object&quot; UserInfo={NSLocalizedDescription=Error decoding object, NSLocalizedFailureReason=Attempted to decode store response})

I cannot request information about the products, nor make purchases with a sand box account. However, it works fine in iOS 12.1 on my device. It does not work with the iPhone 11 simulator or an actual device with iOS 13.

I have found a lot, that the *Xcode 11 GM seed 1* beta simulator had this problem, but have not found a solution yet. I also tested it with the new released *Xcode 11 GM seed 2* version, but there was no fix for me.

Does anyone have a solution on how I can request and purchase In App Purchases again with iOS 13 installed?

Requesting an In App Purchase in iOS 13 fails

How to create grid of square items (for example like in iOS Photo Library) with SwiftUI? 

I tried this approach but it doesn&#39;t work:

    var body: some View {
        List(cellModels) { _ in
            Color.orange.frame(width: 100, height: 100)
        }
    }
    
List still has UITableView style:

[![enter image description here][1]][1]


  [1]: https://i.stack.imgur.com/tyrV8.jpg

UICollectionView and SwiftUI?

What is alternate of `scanHexInt32` in iOS 13 (Swift 5+)?

    extension UIColor {
        
        
        //--------------------------------------------
        class func hexColor(hex:String) -&gt; UIColor {
            var cString:String = hex.trimmingCharacters(in: CharacterSet.whitespacesAndNewlines).uppercased()
            
            if (cString.hasPrefix(&quot;#&quot;)) {
                cString = String(cString[cString.index(cString.startIndex, offsetBy: 1)...])
            }
            
            if (cString.count != 6) {
                return UIColor.gray
            }
            
            var rgbValue:UInt32 = 0
    
    // warning in this line - &#39;scanHexInt32&#39; was deprecated in iOS 13.0
            Scanner(string: cString).scanHexInt32(&amp;rgbValue)
            
            return UIColor(
                red: CGFloat((rgbValue &amp; 0xFF0000) &gt;&gt; 16) / 255.0,
                green: CGFloat((rgbValue &amp; 0x00FF00) &gt;&gt; 8) / 255.0,
                blue: CGFloat(rgbValue &amp; 0x0000FF) / 255.0,
                alpha: CGFloat(1.0)
            )
        }
    }


Ref: Snapshot

[![enter image description here][1]][1]


  [1]: https://i.stack.imgur.com/Ke1Za.png

&#39;scanHexInt32&#39; was deprecated in iOS 13.0

I can&#39;t seem to find any information or figure out how to set the keyboard type on a TextField for SwiftUI.
It would also be nice to be able to enable the secure text property, to hide passwords etc.

This post shows how to &quot;wrap&quot; a UITextField, but I&#39;d rather not use any UI-controls if I don&#39;t have to.
https://stackoverflow.com/questions/56507839/how-to-make-textfield-become-first-responder

Anyone have any ideas how this can be done without wrapping an old school UI control?

How to set Keyboard type of TextField in SwiftUI?

I&#39;ve updated my iOS app to work in dark mode on iOS 13 but I am having trouble trying to get the launch screen to look good.

Currently it is a bright white screen with the app logo which looks awful in dark mode. I have tried setting the background colour of the launch screen to be a colour asset that I made with &quot;Any Appearance&quot; being white and &quot;Dark Appearance&quot; being black - but the launch screen still always shows as white.

Is there any way to get my launch screen to work properly in dark mode?

Dark mode launch screen in iOS 13

I&#39;m using Core Data with Cloud Kit, and have therefore to check the iCloud user status during application startup. In case of problems I want to issue a dialog to the user, and I do it using ```UIApplication.shared.keyWindow?.rootViewController?.present(...)``` up to now.

In Xcode 11 beta 4, there is now a new deprecation message, telling me:

&gt;&#39;keyWindow&#39; was deprecated in iOS 13.0: Should not be used for applications that support multiple scenes as it returns a key window across all connected scenes

How shall I present the dialog instead?

How to resolve: &#39;keyWindow&#39; was deprecated in iOS 13.0

**iOS 13** introduces a new design of `modalPresentationStyle` `.pageSheet` (and its sibling `.formSheet`) for modally presented view controllers…

[![The new sliding modal presentation in iOS 13][1]][1]

…and we can dismiss these sheets by sliding the presented view controller down *(interactive dismissal)*. Although the new &quot;pull-to-dismiss&quot; feature is pretty useful, it may not always be desirable. 

**THE QUESTION:** How can we turn the interactive dismissal off? 
*- Bear in mind we keep the presentation style the same.*

  [1]: https://i.stack.imgur.com/IIoCCm.png

Disable the interactive dismissal of presented view controller

I&#39;m currently using Xcode 11 Beta 5. Within my application, it runs fine on iOS 12 and under. However, on iOS 13 it looks like it&#39;s using the `UIScene` by default. This is causing my app to not do anything. 

When the app launches on fresh install, there is a terms and conditions the user must accept. After agreeing they go to a loading screen which then directs them to the main view. In the screenshot I posted, the view behind the current one in foreground is the splash loading screen. 

We will look into adding multiple views scene support throughout the application soon, but right now we have higher priority stuff we need to work on.

[![](https://imgur.com/i0qLhAL.png)](https://i.imgur.com/i0qLhAL.jpg)

&quot;Support multiple windows&quot; is already disabled in the General settings of the app&#39;s target. Also I have Enable Multiple Windows set to NO in the info.plist file. 


So far nothing has really worked. Basically I want to opt out/disable multiple windows and UIScene/SwiftUI to restore the original behaviour in iOS 10-12. Is this possible in iOS 13 or we have to update it?

Update:

Here is a screenshot of the view debug hierarchy. Left side is iOS 12, right side is on iOS 13. Without adding anything to the Info.plist nor any scene delegate classes or methods, why is it different? Pretty much just ran it in its existing production ready code on Xcode 11.

[![](https://imgur.com/C3aLsDo.png)](https://imgur.com/C3aLsDo)


Opt out of UISceneDelegate/SwiftUI on iOS

Before iOS 13, presented view controllers used to cover the entire screen. And, when dismissed, the parent view controller `viewDidAppear` function were executed.

Now iOS 13 will present view controllers as a sheet as default, which means the card will partially cover the underlying view controller, which means that `viewDidAppear` will not be called, because the parent view controller has never actually disappeared.

Is there a way to **detect that the presented view controller sheet was dismissed**? Some other function I can override in the parent view controller **rather than using some sort of delegate**?

Detecting sheet was dismissed on iOS 13

A `UISegmentedControl` has a new appearance in iOS 13 and existing code to alter the colors of the segmented control no longer work as they did.

Prior to iOS 13 you could set the `tintColor` and that would be used for the border around the segmented control, the lines between the segments, and the background color of the selected segment. Then you could change the color of the titles of each segment using the foreground color attribute with `titleTextAttributes`.

Under iOS 13, the `tintColor` does nothing. You can set the segmented control&#39;s `backgroundColor` to change the overall color of the segmented control. But I can&#39;t find any way to alter the color used as the background of the selected segment. Setting the text attributes still works. I even tried setting the background color of the title but that only affects the background of the title, not the rest of the selected segment&#39;s background color.

In short, how do you modify the background color of the currently selected segment of a `UISegmentedControl` in iOS 13? Is there a proper solution, using public APIs, that doesn&#39;t require digging into the private subview structure?

There are no new properties in iOS 13 for `UISegmentedControl` or `UIControl` and none of the changes in `UIView` are relevant.

How to change the colors of a segment in a UISegmentedControl in iOS 13?

In iOS 13 there is a new behaviour for modal view controller when being presented.

Now it&#39;s not fullscreen by default and when I try to slide down, the app just dismiss the View Controller automatically.

How can I prevent this behaviour and get back to the old fullscreen modal vc?

[![modal behaviour][1]][1]

Thanks


  [1]: https://i.stack.imgur.com/8wo6K.png

Presenting modal in iOS 13 fullscreen

In iOS 13 modal presentations using the form and page sheet style can be dismissed with a pan down gesture. This is problematic in one of my form sheets because the user draws into this box which interferes with the gesture. It pulls the screen down instead of drawing a vertical line.

How can you disable the vertical swipe to dismiss gesture in a modal view controller presented as a sheet?

Setting `isModalInPresentation = true` still allows the sheet to be pulled down, it just won&#39;t dismiss.

Disable gesture to pull down form/page sheet modal presentation

My application isn&#39;t prepared for Dark Mode and I&#39;m not going to work on it today.

Is there a way to disable Dark Mode changes for my app?

iOS 13 disable Dark Mode changes

Been playing around with SwiftUI and understood the concept of `BindableObjects` etc so far (at least I hope I do). 

I bumped into a stupid problem I can&#39;t seem to find an answer for: 
How do you initialize a `@Binding` variable?

I have the following code:

```swift
struct LoggedInView : View {

    @Binding var dismissView: Bool

    var body: some View {
        VStack {
            Text(&quot;Hello World&quot;)
        }
    }
}
```
In my preview code, I want to pass that parameter of type `Binding&lt;Bool&gt;`:

```swift
#if DEBUG
struct LoggedInView_Previews : PreviewProvider {
    static var previews: some View {
        LoggedInView(dismissView: **Binding&lt;Bool&gt;**)
    }
}
#endif
```

How would I go an initialize it? tried:

```swift
Binding&lt;Bool&gt;.init(false)
Binding&lt;Bool&gt;(false)
```

Or even:

```swift
@Binding var dismissView: Bool = false
```

But none worked... any ideas?



SwiftUI @Binding Initialize

A large part of my app consists of web views to provide functionality not yet available through native implementations. The web team has no plans to implement a dark theme for the website. As such, my app will look a bit half/half with Dark Mode support on iOS 13.

Is it possible to opt out of Dark Mode support such that our app always shows light mode to match the website theme?

Is it possible to opt-out of dark mode on iOS 13?

[![Problems demo][1]][1]


  [1]: https://i.stack.imgur.com/L5bfJ.png


Pre-conditions to reproduce the problem:

1. Xcode 11 beta + iOS 13 (latest version until Jun. 12 2019)
2. The navigation bar is in Large text mode
3. Specify the colour of navigation bar.

The status bar will remain in white in a real device, above the green navigation bar. 

Solutions I tried:

1. Revert it back to iOS12 will solve it, but we will encounter iOS13 eventually...
2. disabling the large text mode will solve it...
3. hide the status bar will fix it, but it will cause status text overlapping with navigation bar item.

Any ideas? appreciate any help.




In iOS13 the status bar background colour is different from the navigation bar in large text mode

With the arrival of **iOS 13** statusBar&#39;s view is no longer accessible trough:
 

    value(forKey: &quot;statusBar&quot;) as? UIView

Due to:

&gt; Terminating app due to uncaught exception
&gt; &#39;NSInternalInconsistencyException&#39;, reason: &#39;App called -statusBar or
&gt; -statusBarWindow on UIApplication: this code must be changed as there&#39;s no longer a status bar or status bar window. Use the
&gt; statusBarManager object on the window scene instead.&#39;

But it&#39;s not clear how it should be used for changing colours as `keyWindow?.windowScene?.statusBarManager` does not appear to contain anything related to it.

**I&#39;m compiling my code with (iOS 10, *) compatibility, so I intend to continue using UIKit.**

**Any ideas regarding this subject?**

How to change the status bar background color and text color on iOS 13?

I&#39;ve an app that uses **WkWebView** to play audio from Soundcloud, on iOS 13 Beta 6 the audio stops when the app is not in foreground,
even when **Audio** is on in **Background Modes**.

When starting the playback this assertion is thrown:

    Error acquiring assertion: &lt;NSError: 0x282cf67c0; domain: RBSAssertionErrorDomain; code: 2; reason: &quot;Required client entitlement is missing&quot;&gt; {
    userInfo = {
        RBSAssertionAttribute = &lt;RBSLegacyAttribute: 0x1592432e0; requestedReason: MediaPlayback; reason: MediaPlayback; flags: PreventTaskSuspend | PreventTaskThrottleDown | WantsForegroundResourcePriority&gt;;
    } 
   
And after entering background state, the following assertion is thrown and the audio is suspended:

    Can&#39;t end BackgroundTask: no background task exists with identifier 13 (0xd), or it may have already been ended. Break in UIApplicationEndBackgroundTaskError() to debug. 
    [ProcessSuspension] Background task expired while holding WebKit ProcessAssertion (isMainThread? 1).

This is not happening in iOS 12, where the audio plays normally when it is in background.


iOS 13 - WkWebView: audio stops when in background

We are facing the following networking error when the response is somehow large(14kb) on iOS 13. 

`[-1103] Error Domain=NSURLErrorDomain Code=-1103 &quot;resource exceeds maximum size&quot;`

As we are using Alamofire, this problem is treated as error result which breaks our treatments of the results.

The strange thing is that if we use NSURLSession directly, though this error is still seen from logging, we don&#39;t actually receive it in the callback of 

    session.dataTask(with: request) { value, response, error in ... }

So the result can treated correctly.

This problem is never seen before. Anyone has got some idea on that ?

-1103 Error Domain=NSURLErrorDomain Code=-1103 &quot;resource exceeds maximum size&quot; iOS 13

I am using Xcode 11 and building an app for iOS 13. In a new project I created in Xcode some of the UIApplicationDelegate methods were missing so I added them back into the app delegate file. The new template for a &quot;Single View App&quot; project was missing the methods. The problem is that none of the delegate methods are getting called except `-application:didFinishLaunchingWithOptions:`. Here is my app delegate:

	@implementation AppDelegate

	- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
		NSLog(@&quot;application:didFinishLaunchingWithOptions:&quot;);
		return YES;
	}

	- (void)applicationDidEnterBackground:(UIApplication *)application {
		NSLog(@&quot;applicationDidEnterBackground:&quot;);
	}

	- (void)applicationWillEnterForeground:(UIApplication *)application {
		NSLog(@&quot;applicationWillEnterForeground:&quot;);
	}
	#pragma mark - UISceneSession lifecycle

	- (UISceneConfiguration *)application:(UIApplication *)application configurationForConnectingSceneSession:(UISceneSession *)connectingSceneSession options:(UISceneConnectionOptions *)options {
		return [[UISceneConfiguration alloc] initWithName:@&quot;Default Configuration&quot; sessionRole:connectingSceneSession.role];
	}

	- (void)application:(UIApplication *)application didDiscardSceneSessions:(NSSet&lt;UISceneSession *&gt; *)sceneSessions {
	}

	@end



App delegate methods aren&#39;t being called in iOS 13

I&#39;m trying to recreate a Modal just like Safari in iOS13 in SwiftUI:

Here&#39;s what it looks like:

[![enter image description here][1]][1]

Does anyone know if this is possible in **SwiftUI**? I want to show a small half modal, with the option to drag to fullscreen, just like the sharing sheet.

Any advice is much appreciated! 


  [1]: https://i.stack.imgur.com/CvGYT.png

SwiftUI - Half modal?

After Apple&#39;s iOS 13 release, I realized **`window.navigator.userAgent`** in Safari on iPad iOS 13 is same as on MacOS. Something like this:

```Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.0 Safari/605.1.15```

As you see, it&#39;s a wrong user-agent for iPad and there is no way to detect if the current device is an iDevice.

-----------------
After an initial research, I found a workaround for it:
&gt;Go to Settings -&gt; Safari -&gt; Request Desktop Website -&gt; All websites. You notice &quot;All websites&quot; is **enabled by default**. If you **disable** it and get window.navigator.userAgent the correct user agent is now displayed.

But I cannot ask each user to do this setting change for each device. So I tried to find another way and ended up by writing **the following code which checks if it&#39;s Safari, macOS, and touch-screen then the device should be an apple mobile device**, but I&#39;m wondering is there any better suggestion/way to detect the correct device name in Safari iOS 13?


```javascript
detectOs = function(){
   //returns OS name, like &quot;mac&quot;
};

//is Safari on an apple touch-screen device
isSafariInIdevice = function(){
   if (/Safari[\/\s](\d+\.\d+)/.test(windows.navigator.userAgent)) {
      return &#39;ontouchstart&#39; in window &amp;&amp; detectOs() === &quot;mac&quot;;      
   }
   return false;
};
```

How to detect device name in Safari on iOS 13 while it doesn&#39;t show the correct user agent?

Starting from iOS/iPadOS 13, a dark user interface style is available, similar to the dark mode introduced in macOS Mojave. How can I check whether the user has enabled the system-wide dark mode? 

How can I check whether dark mode is enabled in iOS/iPadOS?

I have following code in my AppDelegate.swift to setup root view controller for an iOS application. But it does not work. It follows Target structure (defined under General tab) and ignores this code.

(Xcode 11, Swift 5.1, iOS 13)

    class AppDelegate: UIResponder, UIApplicationDelegate {
        
        var window: UIWindow?
        
        func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -&gt; Bool {
            
            window = UIWindow(frame: UIScreen.main.bounds)
            guard let rootVC = UIViewController() else {
                print(&quot;Root VC not found&quot;)
                return true
            }
            let rootNC = UINavigationController(rootViewController: rootVC)
            window?.rootViewController = rootNC
            window?.makeKeyAndVisible()
      
            return true
        }
    }

Unable to understand where is the issue. 

I tried following references also but no luck:

   - [Swift ios set a new root view controller][1]
   - [Root View Controller Swift][2]
   - [iOS: Root Controller Navigation][3]


  [1]: https://stackoverflow.com/questions/33374272/swift-ios-set-a-new-root-view-controller
  [2]: https://stackoverflow.com/questions/31062108/root-view-controller-swift
  [3]: https://medium.com/@stasost/ios-root-controller-navigation-3625eedbbff

iOS 13: Swift - &#39;Set application root view controller programmatically&#39; does not work

In iOS 13 `UIApplication.shared.statusBarFrame.height` warns

&gt; &#39;statusBarFrame&#39; was deprecated in iOS 13.0: Use the statusBarManager
&gt; property of the window scene instead.

How do you get the status bar height without using a deprecated API in iOS 13?

How to get the status bar height in iOS 13?

So I have a `ScrollView` holding a set of views:

		ScrollView {
			ForEach(cities) { city in
				NavigationLink(destination: ...) {
					CityRow(city: city)
				}
				.buttonStyle(BackgroundButtonStyle())
			}
		}

In every view I have a drag gesture:

		let drag = DragGesture()
			.updating($gestureState) { value, gestureState, _ in
				// ...
			}
			.onEnded { value in
				// ...
			}

Which I assign to a part of the view:

		ZStack(alignment: .leading) {
			HStack {
				// ...
			}
			HStack {
				// ...
			}
			.gesture(drag)
		}

As soon as I attach the gesture, the `ScrollView` stop scrolling. The only way to make it scroll it to start scrolling from a part of it which has no gesture attached. How can I avoid it and make both work together. In UIKit is was as simple as specifying `true` in `shouldRecognizeSimultaneouslyWith` method. How can I have the same in SwiftUI?

In SwiftUI I&#39;ve tried attaching a gesture using `.simultaneousGesture(drag)` and `.highPriorityGesture(drag)` – they all work the same as `.gesture(drag)`. I&#39;ve also tried providing all possible static `GestureMask` values for `including:` parameter – I have either scroll working or my drag gesture working. Never both of them.


Here&#39;s what I&#39;m using drag gesture for:
[![enter image description here][1]][1]


  [1]: https://i.stack.imgur.com/CRhSi.gif

Adding a drag gesture in SwiftUI to a View inside a ScrollView blocks the scrolling

Since I installed the **iOS 13.2 beta**, I have been getting a debug console error message. It happens every time I load a ViewController with a WKWebView object in the storyboard.


Then the following message is shown continuously while the web view is visible
...

    2019-10-10 12:10:47.867830+0200 (...) [Process] kill() returned unexpected error 1  
    2019-10-10 12:10:47.908698+0200 (...) [Process] kill() returned unexpected error 1  
    2019-10-10 12:10:47.908814+0200 (...) [Process] kill() returned unexpected error 1  
    2019-10-10 12:10:47.934169+0200 (...) [Process] kill() returned unexpected error 1  
    2019-10-10 12:10:47.947668+0200 (...) [Process] kill() returned unexpected error 1  
    2019-10-10 12:10:47.964375+0200 (...) [Process] kill() returned unexpected error 1  
    2019-10-10 12:10:48.193556+0200 (...) [Process] kill() returned unexpected error 1  
    2019-10-10 12:10:48.193723+0200 (...) [Process] kill() returned unexpected error 1  
    2019-10-10 12:10:48.193941+0200 (...) [Process] kill() returned unexpected error 1  
    2019-10-10 12:10:48.194012+0200 (...) [Process] kill() returned unexpected error 1  
    2019-10-10 12:10:48.195679+0200 (...) [Process] kill() returned unexpected error 1  
    2019-10-10 12:10:48.200432+0200 (...) [Process] kill() returned unexpected error 1  
    2019-10-10 12:10:48.207225+0200 (...) [Process] kill() returned unexpected error 1  
    2019-10-10 12:10:48.207298+0200 (...) [Process] kill() returned unexpected error 1 

At the moment I close the view I get the following message: 

    2019-10-10 12:32:41.577505+0200 (...)[ProcessSuspension] 0x1051e50b0 - ProcessAssertion::processAssertionWasInvalidated() 

Sometimes I get the following message in the middle while the web view is loaded: (I can&#39;t say when it happens)
 
    2019-10-10 12:33:11.453528+0200 (...) Could not signal service com.apple.WebKit.WebContent: 113: Could not find specified service
    2019-10-10 12:33:11.459713+0200 (...) Could not signal service com.apple.WebKit.Networking: 113: Could not find specified service

And the if I touch the screen it starts again

        2019-10-10 12:10:48.200432+0200 (...) [Process] kill() returned unexpected error 1  
        2019-10-10 12:10:48.207225+0200 (...) [Process] kill() returned unexpected error 1  
        2019-10-10 12:10:48.207298+0200 (...) [Process] kill() returned unexpected error 1 
    ...




I have checked that this is happening in all of the view controllers with WKWebViews of my app, so it doesn&#39;t seem to be a code error. 

This **doesn&#39;t crash the app**, but I would like to know why this is happening, and if someone else is having the same issue. 



All Ios13 Solutions on Gang of Coders

Total of 27 Ios13 Solutions