tencent cloud

Cloud Object Storage

Release Notes and Announcements
Release Notes
Announcements
Product Introduction
Overview
Features
Use Cases
Strengths
Concepts
Regions and Access Endpoints
Specifications and Limits
Service Regions and Service Providers
Billing
Billing Overview
Billing Method
Billable Items
Free Tier
Billing Examples
Viewing and Downloading Bill
Payment Overdue
FAQs
Getting Started
Console
Getting Started with COSBrowser
User Guide
Creating Request
Bucket
Object
Data Management
Batch Operation
Global Acceleration
Monitoring and Alarms
Operations Center
Data Processing
Content Moderation
Smart Toolbox
Data Processing Workflow
Application Integration
User Tools
Tool Overview
Installation and Configuration of Environment
COSBrowser
COSCLI (Beta)
COSCMD
COS Migration
FTP Server
Hadoop
COSDistCp
HDFS TO COS
GooseFS-Lite
Online Tools
Diagnostic Tool
Use Cases
Overview
Access Control and Permission Management
Performance Optimization
Accessing COS with AWS S3 SDK
Data Disaster Recovery and Backup
Domain Name Management Practice
Image Processing
Audio/Video Practices
Workflow
Direct Data Upload
Content Moderation
Data Security
Data Verification
Big Data Practice
COS Cost Optimization Solutions
Using COS in the Third-party Applications
Migration Guide
Migrating Local Data to COS
Migrating Data from Third-Party Cloud Storage Service to COS
Migrating Data from URL to COS
Migrating Data Within COS
Migrating Data Between HDFS and COS
Data Lake Storage
Cloud Native Datalake Storage
Metadata Accelerator
GooseFS
Data Processing
Data Processing Overview
Image Processing
Media Processing
Content Moderation
File Processing Service
File Preview
Troubleshooting
Obtaining RequestId
Slow Upload over Public Network
403 Error for COS Access
Resource Access Error
POST Object Common Exceptions
API Documentation
Introduction
Common Request Headers
Common Response Headers
Error Codes
Request Signature
Action List
Service APIs
Bucket APIs
Object APIs
Batch Operation APIs
Data Processing APIs
Job and Workflow
Content Moderation APIs
Cloud Antivirus API
SDK Documentation
SDK Overview
Preparations
Android SDK
C SDK
C++ SDK
.NET(C#) SDK
Flutter SDK
Go SDK
iOS SDK
Java SDK
JavaScript SDK
Node.js SDK
PHP SDK
Python SDK
React Native SDK
Mini Program SDK
Error Codes
Harmony SDK
Endpoint SDK Quality Optimization
Security and Compliance
Data Disaster Recovery
Data Security
Cloud Access Management
FAQs
Popular Questions
General
Billing
Domain Name Compliance Issues
Bucket Configuration
Domain Names and CDN
Object Operations
Logging and Monitoring
Permission Management
Data Processing
Data Security
Pre-signed URL Issues
SDKs
Tools
APIs
Agreements
Service Level Agreement
Privacy Policy
Data Processing And Security Agreement
Contact Us
Glossary
DocumentaçãoCloud Object StorageSDK DocumentationiOS SDKTroubleshooting

Troubleshooting

PDF
Modo Foco
Tamanho da Fonte
Última atualização: 2024-01-23 17:15:08
When the SDK request fails, the error field returned is not empty, but instead includes an error code, error description, and other necessary debugging information to help developers quickly fix any issues. Error codes (outlined in the returned error field) include those returned by the client and those returned by the server.

Client Errors

Error codes generated by your device due to network problems are all 4-digit negative numbers, such as -1001. These error codes are defined by Apple. For more information, see the definitions presented in the header file NSURLError.h in Foundation framework.
Custom errors returned by the local client in the SDK network layer includes network exception, invalid certificate and invalid parameter, which is as shown below:
Error Code
Error Message
Error Description
10000
InvalidArgument
Invalid parameter
10001
InvalidCredentials
Invalid certificate
10004
UnsupportOperation
Unsupported operation
20001
InvalidArgument
Invalid data returned by the server
20004
PoorNetwork
A verification for data integrity failed.
30000
UserCancelled
The user has canceled the request.
30002
AlreadyFinished
The job has already finished.

Server Errors

Error codes returned by COS are based on HTTP status codes, such as 404 and 503. For more information on these error codes, see Error Codes. You can also use the self-diagnosis tool to debug the code and quickly locate request errors.

Using the Diagnosis Tool

COS provides a self-help diagnosis tool to help you quickly locate request errors and debug the code.

Directions

1. Copy the RequestId returned by the exception by following directions in Obtaining RequestId.
2. Click Diagnosis Tool.

3. Enter RequestId and click Diagnose.Wait and view the diagnostic result.
Anterior: Setting Access Domain Names (CDN/Global Acceleration)Próximo: Getting Started

Ajuda e Suporte

Esta página foi útil?

comentários