Looks like Apple Distribution and Apple Development are only supported on Xcode 11 which means you won&#39;t be able to use those certificates in Xcode 10 or below. 
## Xcode 11 release note: ##
*Xcode 11 supports the new Apple Development and Apple Distribution certificate types. These certificates support building, running, and distributing apps on any Apple platform. Preexisting iOS and macOS development and distribution certificates continue to work, however, new certificates you create in Xcode 11 use the new types. Previous versions of Xcode don’t support these certificates.*
**source:** https://developer.apple.com/documentation/xcode_release_notes/xcode_11_release_notes

I&#39;m using string literal tables a lot in my C code. These tables all look more or less like this:

    static const char* const stateNames[STATE_AMOUNT] =
    {
        &quot;Init state&quot;,
        &quot;Run state&quot;,
        &quot;Pause state&quot;,
        &quot;Error state&quot;,
    };

The problem with the code above is if the table gets longer and is modified during development, I forget a comma from time to time. The code compiles without a problem with a missing comma, but my program ends up crashing as the last string is set to `NULL`. I used the MinGW and Keil compilers to verify.

Is there any way to generate a compiler warning for my initialization if the comma is missing?

Generate compiler warning if const char* array initialization comma is missing

I get an error when pip builds wheels for the cryptography package.

Error:

[![Error][1]][1]

```
LINK : fatal error LNK1181: cannot open input file &#39;libssl.lib&#39;
  error: command &#39;C:\\Program Files (x86)\\Microsoft Visual Studio\\2017\\BuildTools\\VC\\Tools\\MSVC\\14.16.27023\\bin\\HostX86\\x86\\link.exe&#39; failed with exit status 1181
  ----------------------------------------
  ERROR: Failed building wheel for cryptography
  Running setup.py clean for cryptography
Failed to build cryptography
ERROR: Could not build wheels for cryptography which use PEP 517 and cannot be installed directly
```

I have already installed OpenSSL and set the environment variables as suggested in [this post][2] yet the problem persists. My setup details: 

 - System - Windows 10 
 - Python - 3.8  
 - Pip - 19.3.1

  [1]: https://i.stack.imgur.com/2F20z.png
  [2]: https://stackoverflow.com/a/22210069/7199817

ERROR: Could not build wheels for cryptography which use PEP 517 and cannot be installed directly

It may sound, (let&#39;s say) naive, but I don&#39;t know which certificate I should use for mobile (iOS) apps.

The obvious option would be iOS Distribution certificate, but on the Apple Distribution certificate, the explanation is:

&gt; ...For use with Xcode 11 or later.

Since I&#39;m using Xcode 11, I&#39;m confused. It feels like the Apple Certificate replaces the iOS certificate when using Xcode 11 and later.

Is that correct? Or should I keep using the iOS Distribution for iOS apps?

Should I use iOS Distribution or Apple Distribution certificates for a mobile app?

It may sound, (let's say) naive, but I don't know which certificate I should use for mobile (iOS) apps.
The obvious option would be iOS Distribution certificate, but on the Apple Distribution certificate, the explanation is:
> ...For use with Xcode 11 or later.
Since I'm using Xcode 11, I'm confused. It feels like the Apple Certificate replaces the iOS certificate when using Xcode 11 and later.
Is that correct? Or should I keep using the iOS Distribution for iOS apps?

I have tried to upload an application to Test Flight. The app is successfully validated.

However, when distributing, Xcode is stuck in the &quot;Uploading&quot; stage as shown below:

 &gt; Uploading  
 &gt; Uploading package to the App Store...

[![Uploading package to the App Store...][1]][1]

I have waited 2 hours and nothing has changed.

I am using Xcode 11.1. Is there any solution for this problem?

  [1]: https://i.stack.imgur.com/yUYbP.png

Xcode stuck in &quot;Uploading package to the App Store&quot; stage while uploading

I recently updated my Xcode to 11.4. When I run the app on the device, i&#39;ve noticed that all my navigations item&#39;s titles gone fully black when being set from storyboard.
[![enter image description here][1]][1]

You can&#39;t change neither from code, the following line of code doesn&#39;t work anymore

```swift
self.navigationController?.navigationBar.titleTextAttributes = [.foregroundColor: UIColor.white]
```

I only make it work using some iOS 13 stuffs UINavigationBarAppearance

```swift
@available(iOS 13.0, *)
    private func setupNavigationBar() {
        let app = UINavigationBarAppearance()
        app.titleTextAttributes = [.foregroundColor: UIColor.white]
        app.backgroundColor = Constants.Color.barColor
        self.navigationController?.navigationBar.compactAppearance = app
        self.navigationController?.navigationBar.standardAppearance = app
        self.navigationController?.navigationBar.scrollEdgeAppearance = app
        
        self.navigationController?.navigationBar.titleTextAttributes = [.foregroundColor: UIColor.white]
    }
```

Can somebody explain me why??? This is a crucial bug, or some new hidden feature?


[1]: https://i.stack.imgur.com/FC4Ei.png

Xcode 11.4. Navigation&#39;s Title Color gone BLACK from storyboard

When I integrate a [local package][1] in my Xcode project everything is fine initially but when i switch branches and want to run the app Xcode gives me the compile error `Missing package product &lt;package name&gt;`. When I quit Xcode and re-open it everything is fine again. Any idea what this can be? An Xcode bug?

We also integrate external packages via Swift Package Manager which works perfectly fine. No issues there.

The issue is also well described in a [post by Jesse Squires][2].


  [1]: https://developer.apple.com/documentation/xcode/creating_a_standalone_swift_package_with_xcode
  [2]: https://www.jessesquires.com/blog/another-issue-with-swiftpm-xcode-integration/

Xcode 11.4 compile error &#39;Missing package product &lt;package name&gt;&#39;

After upgrading to Xcode 11.3.1, I am having problems using Safari web inspector with the iOS 12.1 simulator. Every time that I run an app inside of an iOS 12.1 simulator device, it will show up in the Safari debug menu and allow me to connect to it, but the only tabs I will see are Sources, Console and Audit. 

Here is a screenshot of the inspector attached to an instance of the Safari browser inside of the simulator.

[![enter image description here][1]][1]


Is there any way to resolve this?


  [1]: https://i.stack.imgur.com/Lch96.png

Environment:

 - MacOS 10.14.6 (18G95)
 - Xcode 11.3.1
 - Safari 13.1 (14609.1.20.111.8)
 - Simulator Version 11.3.1 (SimulatorApp-912.5.1 SimulatorKit-570.3
   CoreSimulator-681.17.2)



Safari web inspector is only showing Sources, Console and Audit

I try to do the architecture for a bigger, production ready SwiftUI App. I am running all the time into the same problem which points to a major design flaw in SwiftUI.

Still nobody could give me a full working, production ready answer. 

**How to do reusable Views in `SwiftUI` which contain navigation?** 

As the `SwiftUI` `NavigationLink` is strongly bound to the view this is simply not possible in such a way that it scales also in bigger Apps. `NavigationLink` in those small sample Apps works, yes - but not as soon as you want to reuse many Views in one App. And maybe also reuse over module boundaries. (like: reusing View in iOS, WatchOS, etc...)

The design problem: NavigationLinks are hardcoded into the View.

    NavigationLink(destination: MyCustomView(item: item))

But if the view containing this `NavigationLink` should be reusable **I can not hardcode** the destination. There has to be a mechanism which provides the destination. I asked this here and got quite a good answer, but still not the full answer:

https://stackoverflow.com/questions/61188131/swiftui-mvvm-coordinator-router-navigationlink/61188788#61188788

The idea was to inject the Destination Links into the reusable view. Generally the idea works but unfortunately this does not scale to real Production Apps. As soon as I have multiple reusable screens I run into the logical problem that one reusable view (`ViewA`) needs a preconfigured view-destination (`ViewB`). But what if `ViewB` also needs a preconfigured view-destination `ViewC`? I would need to create `ViewB` already in such a way that `ViewC` is injected already in `ViewB` before I inject `ViewB` into `ViewA`. And so on.... but as the data which at that time has to be passed is not available the whole construct fails.

Another idea I had was to use the `Environment` as dependency injection mechanism to inject destinations for `NavigationLink`. But I think this should be considered more or less as a hack and not a scalable solution for large Apps. We would end up using the Environment basically for everything. But because Environment also can be used **only** inside View&#39;s (not in separate Coordinators or ViewModels) this would again create strange constructs in my opinion.

Like business logic (e.g. view model code) and view have to be separated also navigation and view have to be separated (e.g. the Coordinator pattern) In `UIKit` it&#39;s possible because we access to `UIViewController` and `UINavigationController` behind the view. `UIKit&#39;s` MVC already had the problem that it mashed up so many concepts that it become the fun-name &quot;Massive-View-Controller&quot; instead of &quot;Model-View-Controller&quot;. Now a similar problem continues in `SwiftUI` but even worse in my opinion. Navigation and Views are strongly coupled and can not be decoupled. Therefore it&#39;s not possible to do reusable views if they contain navigation. It was possible to solve this in `UIKit` but now I can&#39;t see a sane solution in `SwiftUI`. Unfortunately Apple did not provide us an explanation how to solve architectural issues like that. We got just some small sample Apps.

I would love to be proven wrong. Please show me a clean App design pattern which solves this for big production ready Apps. 

Thanks in advance.

------- 

Update: this bounty will end in a few minutes and unfortunately still nobody was able to provide a working example. But I will start a new bounty to solve this problem if I can&#39;t find any other solution and link it here. Thanks to all for their great Contribution!

--------
Update 18th June 2020:
I got an answer from Apple regarding this issue, proposing something like this to decouple views and models:


    enum Destination {
      case viewA
      case viewB 
      case viewC
    }
    
    struct Thing: Identifiable {
      var title: String
      var destination: Destination
      // … other stuff omitted …
    }
    
    struct ContentView {
      var things: [Thing]
    
      var body: some View {
        List(things) {
          NavigationLink($0.title, destination: destination(for: $0))
        }
      }
    
      @ViewBuilder
      func destination(for thing: Thing) -&gt; some View {
        switch thing.destination {
          case .viewA:
            return ViewA(thing)
          case .viewB:
            return ViewB(thing)
          case .viewC:
            return ViewC(thing)
        }
      }
    }


My response was:

&gt; Thanks for the feedback. But as you see you still have the strong
&gt; coupling in the View. Now &quot;ContentView&quot; needs to know all the views
&gt; (ViewA, ViewB, ViewC) it can navigate too. As I said, this works in
&gt; small sample Apps, but it does not scale to big production ready Apps.
&gt; 
&gt; 
&gt; Imagine that I create a custom View in a Project in GitHub. And then
&gt; import this view in my App. This custom View does not know anything
&gt; about the other views it can navigate too, because they are specific
&gt; to my App. 
&gt; 
&gt; I hope I explained the problem better.  
&gt; 
&gt; The only clean solution I see to this problem is to separate
&gt; Navigation and Views like in UIKit. (e.g. UINavigationController)
&gt; 
&gt; Thanks, Darko


So still no clean &amp; working solution for this problem. Looking forward to WWDC 2020. 

-------------

Update September 2021:
Using `AnyView` is not a good general solution for this problem. In big Apps basically all views have to be designed in a reusable way. This would mean that `AnyView` get&#39;s used _everywhere_. I had a session with two Apple developers and they clearly explained to me the `AnyView` creates a way worse performance then View and it should be only used in exceptional cases. The underlying reason for this is that the type of `AnyView` can&#39;t be resolved during compile time so it has to be allocated on the heap. 

SwiftUI - how to avoid navigation hardcoded into the view?

I am aware that [Let&#39;s Encrypt][1] made changes that may impact older clients because a root certificate would expire. See *[DST Root CA X3 Expiration (September 2021)][2]*.

However, I didn&#39;t think this could impact me because my development machine is up-to-date.

But since today I get the message while doing a `git pull`:

```lang-none
fatal: unable to access &#39;https://git.company.tld/project.git/&#39;: SSL certificate problem: certificate has expired
```

I just downloaded the newest Git for Windows (2.33.0) and confirmed that the built-in [OpenSSL][3] is up-to-date (`OpenSSL 1.1.1k  25 Mar 2021`) which should be good.

*[OpenSSL Client Compatibility Changes for Let’s Encrypt Certificates][4]*

But the error seems to stay.

    openssl s_client -showcerts -connect git.company.tld:443

shows

```lang-none
CONNECTED(000001A0)
---
Certificate chain
 0 s:CN = git.company.tld
   i:C = US, O = Let&#39;s Encrypt, CN = R3
-----BEGIN CERTIFICATE-----
...
-----END CERTIFICATE-----
 1 s:C = US, O = Let&#39;s Encrypt, CN = R3
   i:O = Digital Signature Trust Co., CN = DST Root CA X3
-----BEGIN CERTIFICATE-----
...
-----END CERTIFICATE-----
---
Server certificate
subject=CN = git.company.tld

issuer=C = US, O = Let&#39;s Encrypt, CN = R3

---
No client certificate CA names sent
Peer signing digest: SHA512
Peer signature type: RSA
Server Temp Key: ECDH, P-256, 256 bits
---
SSL handshake has read 3058 bytes and written 443 bytes
Verification error: certificate has expired
---
New, TLSv1.2, Cipher is ECDHE-RSA-AES256-GCM-SHA384
Server public key is 2048 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
    Protocol  : TLSv1.2
    Cipher    : ECDHE-RSA-AES256-GCM-SHA384
    Session-ID: ...
    Session-ID-ctx:
    Master-Key: ...
    PSK identity: None
    PSK identity hint: None
    SRP username: None
    Start Time: 1632982992
    Timeout   : 7200 (sec)
    Verify return code: 10 (certificate has expired)
    Extended master secret: no
---
```

The problem is not with the issued certificate itself which is not expired and accepted by Chrome (Windows [certificate store][5]) and Firefox.

  [1]: https://en.wikipedia.org/wiki/Let&#39;s_Encrypt
  [2]: https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/
  [3]: https://en.wikipedia.org/wiki/OpenSSL
  [4]: https://community.letsencrypt.org/t/openssl-client-compatibility-changes-for-let-s-encrypt-certificates/143816
  [5]: https://superuser.com/questions/217719/what-are-the-windows-system-certificate-stores



Content Type	Original Author	Original Content on Stackoverflow
Question	Dpedrinha	View Question on Stackoverflow
Solution 1 - Ios	Ricardo Sgobbe	View Answer on Stackoverflow

Should I use iOS Distribution or Apple Distribution certificates for a mobile app?

Ios Problem Overview

Ios Solutions

Solution 1 - Ios

Xcode 11 release note:

ERROR: Could not build wheels for cryptography which use PEP 517 and cannot be installed directly

Generate compiler warning if const char* array initialization comma is missing

Attributions