AppSync realtime endpoint URL is not correct for AWS China regions

[wulianer]

Before opening, please confirm:

• I have searched for duplicate or closed issues and discussions.

Language and Async Model

Java

Amplify Categories

GraphQL API

Gradle script dependencies

// Put output below this line

Environment information

# Put output below this line

Please include any relevant guides or documentation you're referencing

No response

Describe the bug

Working on Android projects with AWS China service region. The AppSync Query/Mutation methods work well but no subscription method works. Looking into the network traffic detail, I found that the Amplify SDK mistakenly processes the AWS China's realtime endpoint URL to a not existing endpoint URL thus causes the subscription failure . Below is the block of source code that needs update:

private val standardEndpointRegex =
    "^https://\\w{26}\\.appsync-api\\.\\w{2}(?:-\\w{2,})+-\\d\\.amazonaws.com/graphql$".toRegex()
    
 private val realtime by lazy {
        if (standardEndpointRegex.matches(urlString)) {
            // For standard URLs we insert "realtime" into the domain
            URL(urlString.replace("appsync-api", "appsync-realtime-api"))
        } else {
            // For custom URLs we append "realtime" to the path
            URL("$urlString/realtime")
        }
    }   

All AWS China region AppSync endpoint URLs end with amazonaws.com.cn thus they will not met the stanadardEndpointRegex and will be added /realtime. This is not correct for these URLs.

Besides above code snippet, there are multiple places that have this similar logic to check if an endpoint is a custom domain URL. All of them need update to support China AWS region

Reproduction steps (if applicable)

No response

Code Snippet

// Put your code below this line.

Log output

// Put your logs below this line

amplifyconfiguration.json

No response

GraphQL Schema

// Put your schema below this line

Additional information and screenshots

No response

[mattcreaser]

Hi @wulianer, thanks for the report. We'll check with the AppSync team about this and get back to you.

[mattcreaser]

The fix for this issue has been merged and will be included in our next release.

[wulianer]

Thank you for the quick response for the fix! @mattcreaser

[mattcreaser]

This fix has been released in Amplify 2.24.1. Please let us know if you have any issues!

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.