Make jwt access token init public #17
pr.yaml
on: pull_request_target
test-orchestrator
45s
static-analysis
2m 50s
Matrix: ios-pr
Annotations
5 errors and 2 warnings
ios-pr (SalesforceSDKCore) / test-ios:
libs/SalesforceSDKCore/SalesforceSDKCore/Classes/Analytics/SFSDKEventBuilderHelper.m#L57
testCredentialsCopying, *** -[__NSPlaceholderDictionary initWithObjects:forKeys:count:]: attempt to insert nil object from objects[0] (NSInvalidArgumentException)
|
ios-pr (SalesforceSDKCore) / test-ios:
libs/SalesforceSDKCore/SalesforceSDKCoreTests/SalesforceRestAPITests.m#L2911
testPublicApiCalls, ((error == nil) is true) failed - RestApi call to a public api should not fail
|
ios-pr (SalesforceSDKCore) / test-ios:
libs/SalesforceSDKCore/SalesforceSDKCoreTests/SalesforceRestAPITests.m#L2912
testPublicApiCalls, ((response == nil) is false) failed - RestApi call to a public api should not have a nil response
|
ios-pr (SalesforceSDKCore) / test-ios:
libs/SalesforceSDKCore/SalesforceSDKCoreTests/SalesforceRestAPITests.m#L2913
testPublicApiCalls, ((response.count > 0) is true) failed - The response should have github/forcedotcom repos
|
ios-pr (SalesforceSDKCore) / test-ios
Error: `xcodebuild` aborted (65)
|
ios-pr (SalesforceSDKCore) / test-ios
We feel you. CI failures suck. Download the `.xcresult` files we just artifact’d. They *really* help diagnose what went wrong! https://github.com/forcedotcom/SalesforceMobileSDK-iOS/actions/runs/12473186515#artifact
|
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "test#17.0zl44d.xcresult".
Please update your workflow to use v4 of the artifact actions.
Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
test#17.0zl44d.xcresult
|
73.6 MB |
|