blocks|key|1723275|text|当试图为未知的URLCredential从URLCredentialStorage检索URLProtectionSpace时，会发生此错误。例如：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1723276|let+protectionSpace+=+URLProtectionSpace.init(host:+host,+
++++++++++++++++++++++++++++++++++++++++++++++port:+port,+
++++++++++++++++++++++++++++++++++++++++++++++protocol:+"http",+
++++++++++++++++++++++++++++++++++++++++++++++realm:+nil,+
++++++++++++++++++++++++++++++++++++++++++++++authenticationMethod:+nil)

var+credential:+URLCredential?+=+URLCredentialStorage.shared.defaultCredential(for:+protectionSpace)|code-block|syntax|javascript|1723277|产生|1723278|CredStore+-+performQuery+-+Error+copying+matching+creds.++Error=-25300,+query={
++++class+=+inet;
++++"m_Limit"+=+"m_LimitAll";
++++ptcl+=+http;
++++"r_Attributes"+=+1;
++++srvr+=+host;
++++sync+=+syna;
}|1723279|给它一个保护空间的证书：|1723280|let+userCredential+=+URLCredential(user:+user,+
+++++++++++++++++++++++++++++++++++password:+password,+
+++++++++++++++++++++++++++++++++++persistence:+.permanent)

URLCredentialStorage.shared.setDefaultCredential(userCredential,+for:+protectionSpace)|1723281|下次您试图检索凭据时，错误就会消失。|1723282|我有点不知所措，因为我不知道是什么导致了这一切，或者CredStore到底做了什么。CredStore在iOS中有什么用途？|blockquote|1723283|iOS上的凭据存储允许用户在设备上临时或永久地将基于证书或基于密码的凭据安全地存储到密钥链。|1723284|我怀疑您的后端服务器上有某种身份验证，并且该服务器正在请求对您的应用程序进行身份验证挑战(该应用程序不存在凭据)。|1723285|它可能会被安全地忽略，因为从URLCredentialStorage返回的零是一个有效的响应。|1723286|entityMap^0|7|D|L|K|17|I|0|0|0|0|0|0|0|0|0|0|E|K|0^^$0|@$1|2|3|4|5|6|7|15|8|@$9|16|A|17|B|C]|$9|18|A|19|B|C]|$9|1A|A|1B|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|1C|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|1D|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|1E|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|1F|8|@]|D|@]|E|$]]|$1|Q|3|R|5|H|7|1G|8|@]|D|@]|E|$I|J]]|$1|S|3|T|5|6|7|1H|8|@]|D|@]|E|$]]|$1|U|3|V|5|W|7|1I|8|@]|D|@]|E|$]]|$1|X|3|Y|5|6|7|1J|8|@]|D|@]|E|$]]|$1|Z|3|10|5|6|7|1K|8|@]|D|@]|E|$]]|$1|11|3|12|5|6|7|1L|8|@$9|1M|A|1N|B|C]]|D|@]|E|$]]|$1|13|3|-4|5|6|7|1O|8|@]|D|@]|E|$]]]|14|$]]

This error occurs when trying to retrieve an <code>URLCredential</code> from <code>URLCredentialStorage</code> for an unknown <code>URLProtectionSpace</code>.
e.g.

<pre><code>let protectionSpace = URLProtectionSpace.init(host: host, 
 port: port, 
 protocol: "http", 
 realm: nil, 
 authenticationMethod: nil)

var credential: URLCredential? = URLCredentialStorage.shared.defaultCredential(for: protectionSpace)
</code></pre>

produces

<pre><code>CredStore - performQuery - Error copying matching creds. Error=-25300, query={
 class = inet;
 "m_Limit" = "m_LimitAll";
 ptcl = http;
 "r_Attributes" = 1;
 srvr = host;
 sync = syna;
}
</code></pre>

Give it a credential for the protection space:

<pre><code>let userCredential = URLCredential(user: user, 
 password: password, 
 persistence: .permanent)

URLCredentialStorage.shared.setDefaultCredential(userCredential, for: protectionSpace)
</code></pre>

and the error goes away next time you try to retrieve the credential.

<blockquote>
 I am a little lost as I am not sure what is causing this, or what
 CredStore even does. What purpose does CredStore serve in iOS?
</blockquote>

Credential storage on iOS allows users to securely store certificate-based or password-based credentials on the device either temporarily or permanently to the keychain. 

I suspect that you have some sort of authentication on your backend server and that server is requesting an authentication challenge to your app (for which no credential exists). 

It can probably be safely ignored as returning nil from the <code>URLCredentialStorage</code> is a valid response

blocks|key|848283|text|我编辑了包含URL的字符串以解决此问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|848284|var+myUrl+=+"http://myurl.com"
myUrl+=+myUrl.addingPercentEncoding(withAllowedCharacters:+.urlFragmentAllowed)!

let+url+=+URL(string:+myUrl)|code-block|syntax|javascript|848285|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I edited the String that contains the URL to fix this issue:

<pre><code>var myUrl = "http://myurl.com"
myUrl = myUrl.addingPercentEncoding(withAllowedCharacters: .urlFragmentAllowed)!

let url = URL(string: myUrl)
</code></pre>

blocks|key|1723364|text|这是传输错误，让我们在plist文件中添加这样的传输权限：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1723365|<key>NSAppTransportSecurity</key>
++++<dict>
++++++++<key>NSAllowsArbitraryLoads</key>
++++++++<true/>
++++</dict>|code-block|syntax|javascript|1723366|要小心，因为它允许从应用程序连接到任何服务器。在继续之前，请阅读有关应用程序传输安全性的更多信息。见@kezi的评论|offset|length|style|BOLD|1723367|entityMap^0|0|0|0|3|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

This is transport error, let's add transport permission like this in plist file: 

<pre><code>&lt;key&gt;NSAppTransportSecurity&lt;/key&gt;
 &lt;dict&gt;
 &lt;key&gt;NSAllowsArbitraryLoads&lt;/key&gt;
 &lt;true/&gt;
 &lt;/dict&gt;
</code></pre>

Be careful as that enables connection to any server from your app. Read more on App Transport Security before proceeding. See comment by @kezi

blocks|key|935126|text|在我的例子中，我没有用API键初始化Stripe。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|935127|++++++++STPPaymentConfiguration.shared().publishableKey+=+publishableKey|code-block|syntax|javascript|935128|如果有任何条纹操作，我们可以打印错误日志，它很容易理解。|935129|++++++++print(error.debugDescription)|935130|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

In my case, I was not initialising Stripe SDK with API key.

<pre><code> STPPaymentConfiguration.shared().publishableKey = publishableKey
</code></pre>

In case of any Stripe operation, we can print the error log, its easy to understand.

<pre><code> print(error.debugDescription)
</code></pre>

blocks|key|850403|text|如果收到此错误，使用AVPlayer时，只需在主线程上调用.play()即可|type|unstyled|depth|inlineStyleRanges|entityRanges|data|850404|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you get this error, when using AVPlayer, just call .play() on main thread

blocks|key|850408|text|错误也可能是由内容安全策略(CSP)引起的，该策略可能过于限制性。在我们的例子中，我们需要一个或多或少完全开放并允许一切的CSP。请记住，打开CSP可能是一个很大的安全问题(具体取决于您在应用程序中要做什么)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|850409|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The error may also be caused by a Content Security Policy (CSP) that may be too restrictive. In our case, we needed a CSP that is more or less completely open and allows everything. Keep in mind that opening the CSP can be a great security issue (depending on what exactly you're doing in the app).

blocks|key|1723424|text|同样的问题也发生在我身上，我发现如果您的API在URL末尾不包含"/“，那么iOS就不会向服务器发送”授权“值。因此，您将在控制台中看到一条类似于发帖的消息。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1723425|因此，只需在URL末尾添加"/“即可。|1723426|https://example.com/api/devices/|code-block|syntax|javascript|1723427|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

This same issue happens to me and I found that if your API URL does not contain a "/" at the end of URL then iOS does not send "Authorization" value to the server. Due to which you will see a message like posted in question in the console.

So Simply add "/" at the end of URL

<pre><code>https://example.com/api/devices/
</code></pre>

blocks|key|1723429|text|我不知道为什么在使用Alamofire执行请求时会出现这个错误，但是如果您在HTTP头中使用一些标记来处理API请求，那么您可能根本不需要存储凭据。因此，我们可以根据我们的请求禁用它：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1723430|let+configuration+=+URLSessionConfiguration.default
configuration.httpAdditionalHeaders+=+ourHeaders
//+disable+default+credential+store
configuration.urlCredentialStorage+=+nil

let+manager+=+Alamofire.SessionManager(configuration:+configuration)
...|code-block|syntax|javascript|1723431|在这样的更改之后没有错误。|1723432|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I'm not sure why do we get this error when perform requests with Alamofire, but if you do API requests with some token in HTTP headers, you maybe don't need credentials store at all. So we can disable it for our request:

<pre><code>let configuration = URLSessionConfiguration.default
configuration.httpAdditionalHeaders = ourHeaders
// disable default credential store
configuration.urlCredentialStorage = nil

let manager = Alamofire.SessionManager(configuration: configuration)
...
</code></pre>

No errors after such change.

blocks|key|1723468|text|我之所以会出现这个错误，是因为我不小心在授权头中使用了两个空格。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1723469|不正确：|1723470|request.setValue("Bearer++\(accessToken)",+forHTTPHeaderField:+"Authorization")|code-block|syntax|javascript|1723471|正确：|1723472|request.setValue("Bearer+\(accessToken)",+forHTTPHeaderField:+"Authorization")|1723473|简单的错误，但花了一段时间才找到。|1723474|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|U|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

The cause of me getting this error was due to me accidentally using two spaces between the "Bearer" and access token in my Authorization header.

Incorrect:

<pre><code>request.setValue("Bearer \(accessToken)", forHTTPHeaderField: "Authorization")
</code></pre>

Correct:

<pre><code>request.setValue("Bearer \(accessToken)", forHTTPHeaderField: "Authorization")
</code></pre>

Simple mistake, but it took a while to find it.

blocks|key|850467|text|好的，我犯了这个错误，在与我的Rails应用程序交互时，我和它斗争了很长时间(几年)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|850468|我设置了默认凭据，如可接受的答案中所描述的，但仍然得到了错误，并且一直依赖于didReceiveChallenge响应来提供凭据--幸运的是，这是一项工作。|850469|但!我刚找到解决办法！|850470|我的直觉是，protectedSpace字段与Rails服务器的授权挑战不匹配--我查看了领域字段，这似乎是唯一一个未定义的字段。|850471|我从打印服务器响应头开始，虽然我能够检查这些头，但是它们没有包含包含领域字段的WWW-Authorization字段。|850472|我认为这可能是因为我的Rails应用程序没有指定领域，所以我开始关注Rails方面的事情。|850473|我发现我可以在调用中指定领域，|850474|authenticate_or_request_with_http_basic|code-block|syntax|javascript|850475|...which用于HTTP身份验证。|850476|我并没有指定一个领域，所以添加了一个，|850477|authenticate_or_request_with_http_basic("My+Rails+App")|850478|然后我将相应的字符串添加到protectionSpace中，|850479|NSURLProtectionSpace+*protectionSpace+=
++++[[NSURLProtectionSpace+alloc]+initWithHost:@"myrailsapp.com"
++++++++port:443
++++++++protocol:NSURLProtectionSpaceHTTPS
++++++++realm:@"My+Rails+App"
++++++++authenticationMethod:NSURLAuthenticationMethodHTTPBasic];|850480|瞧！这起作用了，我再也不知道，|850481|CredStore+-+performQuery+-+Error+copying+matching+creds.++Error=-25300|850482|即使在Rails应用程序中指定了领域之后，我仍然没有看到它在HTTP头中被传递，我不知道为什么，但至少它能工作。|850483|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1B|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1C|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|1D|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|1E|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|1F|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|1G|8|@]|9|@]|A|$]]|$1|N|3|O|5|P|7|1H|8|@]|9|@]|A|$Q|R]]|$1|S|3|T|5|6|7|1I|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1J|8|@]|9|@]|A|$]]|$1|W|3|X|5|P|7|1K|8|@]|9|@]|A|$Q|R]]|$1|Y|3|Z|5|6|7|1L|8|@]|9|@]|A|$]]|$1|10|3|11|5|P|7|1M|8|@]|9|@]|A|$Q|R]]|$1|12|3|13|5|6|7|1N|8|@]|9|@]|A|$]]|$1|14|3|15|5|P|7|1O|8|@]|9|@]|A|$Q|R]]|$1|16|3|17|5|6|7|1P|8|@]|9|@]|A|$]]|$1|18|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]]|19|$]]

OK, I had this error, and fought with it for a long time (years) when interacting with my Ruby on Rails app.

I had default credentials set up as described in the accepted answer, but still got the error, and have been relying on a didReceiveChallenge response to supply the credentials - fortunately that worked as a work around.

But! I've just found the solution!

I was working on a hunch that that the protectedSpace fields did not match the Authorization challenge from the Ruby on Rails server - and I looked into the realm field, which seemed to be the only one that was being left undefined.

I started by printing out the server response headers, and although I was able to examine these, they did not include the WWW-Authorization field that would have included the realm field.

I thought this was maybe because my Rails app wasn't specifying the realm, so I started looking at the Rails side of things.

I found I could specify the realm in the call to,

<pre><code>authenticate_or_request_with_http_basic
</code></pre>

...which I am using for HTTP Basic authentication.

I wasn't specifying a realm already, so added one,

<pre><code>authenticate_or_request_with_http_basic("My Rails App")
</code></pre>

I then added the corresponding string to the protectionSpace,

<pre><code>NSURLProtectionSpace *protectionSpace =
 [[NSURLProtectionSpace alloc] initWithHost:@"myrailsapp.com"
 port:443
 protocol:NSURLProtectionSpaceHTTPS
 realm:@"My Rails App"
 authenticationMethod:NSURLAuthenticationMethodHTTPBasic];
</code></pre>

Voila! That worked, and I no longer get the,

<pre><code>CredStore - performQuery - Error copying matching creds. Error=-25300
</code></pre>

Even after specifying the realm in the Rails app, I still don't see it passed in the HTTP header, I don't know why, but at least it works.

blocks|key|850498|text|当我试图在网页上打开一个http-页面时，我遇到了这个问题。但是这个页面包含了一个弹出窗口，它是首先打开的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|850499|当后端团队移除这个弹出窗口时，一切都变得正常了。|850500|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I got this issue when I tried to open a http-page inside a web-view. But this page contained an popup which was opened first.

When backend team removed this popup everything became OK.

blocks|key|935340|text|++++let+credentialData+=+"\(user):\(password)".data(using:+String.Encoding.utf8)!
++++let+base64Credentials+=+credentialData.base64EncodedString(options:+[])
++++let+headers+=+["Authorization":+"Basic+\(base64Credentials)"]
++++Alamofire.request(url,+method:+.get,+parameters:+params,encoding:+URLEncoding.default,headers:+headers)
++++++++++++++++.responseJSON{
++++++++++++response+in
++++++++++++guard+let+value+=++response.result.value+else+{return}
++++++++++++++++++++print(value)
+++++}|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|935341|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code> let credentialData = "\(user):\(password)".data(using: String.Encoding.utf8)!
 let base64Credentials = credentialData.base64EncodedString(options: [])
 let headers = ["Authorization": "Basic \(base64Credentials)"]
 Alamofire.request(url, method: .get, parameters: params,encoding: URLEncoding.default,headers: headers)
 .responseJSON{
 response in
 guard let value = response.result.value else {return}
 print(value)
 }
</code></pre>

blocks|key|935375|text|我的问题是用rest调用发送的图像的base64编码。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|935376|我以前用过|935377|let+strBase64+=+imageData.base64EncodedString(options:+.lineLength64Characters)|code-block|syntax|javascript|935378|但是有50%25的时间我会得到上面的错误。|935379|我用下面的方法解决了我的问题.|935380|+let+strBase64+=+imageData.base64EncodedString()|935381|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|F|7|V|8|@]|9|@]|A|$G|H]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

My issue was base64 encoding of an image that was being sent with a rest call
I had previously used
<pre><code>let strBase64 = imageData.base64EncodedString(options: .lineLength64Characters)
</code></pre>
But 50% of the time I would get the error above.
I used the following instead which solved my problem...
<pre><code> let strBase64 = imageData.base64EncodedString()
</code></pre>

blocks|key|1723554|text|Twitter登录时也有同样的问题。结果发现我使用了错误的API密钥。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1723555|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Had the same issue with Twitter sign in. Turned out I used the the wrong API key.

blocks|key|1723564|text|我将.cURLDescription移除|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1723565|AF.request(url)|code-block|syntax|javascript|1723566|那根木头不见了|1723567|entityMap^0|2|G|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|N|$]]

I remove <code>.cURLDescription</code>
on
<pre><code>AF.request(url)
</code></pre>
and that log is gone

blocks|key|935486|text|在使用stripe时，我发现我应该从Stripe中添加可发布的键。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|935487|这是在AppDelegate中设置的，正如在https://stripe.com/docs/development/quickstart第2步中所发现的那样。|offset|length|935488|func+application(_+application:+UIApplication,+didFinishLaunchingWithOptions+launchOptions:+[UIApplication.LaunchOptionsKey:+Any]?)+->+Bool+{
++++++++StripeAPI.defaultPublishableKey+=+"pk_test_....."
++++++++return+true
++++}|code-block|syntax|javascript|935489|entityMap|0|LINK|mutability|MUTABLE|url|https://stripe.com/docs/development/quickstart^0|0|M|1A|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@$D|U|E|V|1|W]]|A|$]]|$1|F|3|G|5|H|7|X|8|@]|9|@]|A|$I|J]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

When working with the Stripe IOS SDK, I found that I should have added the publishable key from stripe.
This is set in AppDelegate, as found in <a href="https://stripe.com/docs/development/quickstart" rel="nofollow noreferrer">https://stripe.com/docs/development/quickstart</a>, step 2.
<pre><code>func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -&gt; Bool {
 StripeAPI.defaultPublishableKey = &quot;pk_test_.....&quot;
 return true
 }

</code></pre>

I am running into an issue while doing API calls to my apps backend, every connection now prompts with

<pre><code>CredStore - performQuery - Error copying matching creds. Error=-25300, query={
 atyp = http;
 class = inet;
 "m_Limit" = "m_LimitAll";
 ptcl = http;
 "r_Attributes" = 1;
 srvr = "myappsurl.com";
 sync = syna;
}
</code></pre>

I am a little lost as I am not sure what is causing this, or what CredStore even does. 
What purpose does CredStore serve in iOS?

CredStore Perform Query error

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我在对我的应用程序后端执行API调用时遇到了一个问题，现在每个连接都会用CredStore - performQuery - Error copying matching creds.  Error=-25300, query={    atyp = http;    class = inet;    "m_Limit...

问CredStore执行查询错误
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问CredStore执行查询错误EN