Error accessing remote repository while updating conversation-ios package to version 3.0.0

[anish190]

I am trying to update the conversation-ios package to version 3.0.0, but I am getting the following error:

https://github.com/twilio/twilsock-ios: The remote repository could not be accessed. Make sure a valid repository exists at the specified location and that the correct credentials have been supplied.

Environment: TwilioConversationsClient v3.3.0

[RicardoNunoAlmeida]

@anish190: we are very sorry for this. We'll set up access to that repo and ping you as soon as it is completed.

[RicardoNunoAlmeida]

Hey @anish190 can you please try again now and let us know how it goes?

[anish190]

Hi @RicardoNunoAlmeida, Thanks for the update. Unfortunately, I am getting another error.

invalid custom path 'Dummy' for target 'TwilioConversationsClientTarget'

[Gray-Wind]

Hello @anish190,

I've just re-published the release, could you please try again?

[anish190]

@Gray-Wind , I am able to compile the project when I directly add conversation-ios to Package dependencies in Xcode. But I want to add it as a dependency to my custom package. I am getting the same error when I add it as a dependency.

invalid custom path 'Dummy' for target 'TwilioConversationsClientTarget'

ChatKit //Package.swift

...
...
dependencies: [
        // Dependencies declare other packages that this package depends on.
        .package(url: "https://github.com/twilio/conversations-ios", from: Version(3, 0, 0))
       ]
...
...
.target(
            name: "ChatKit",
.product(name: "TwilioConversationsClient", package: "conversations-ios"),
])

[Gray-Wind]

Hi @anish190,

Sorry to ask, but did you try to reset SPM caches?

[anish190]

@Gray-Wind Thank you for the suggestion. I actually did try resetting the SPM caches earlier but in the custom kit. However, it didn't work until I reset the SPM caches in the main project. I appreciate your help.

[Gray-Wind]

@anish190 glad to hear that! Do I understand correctly that now it all works fine and this ticket could be closed?

[anish190]

@Gray-Wind Yes. It's working. You can close this issue.