#Clicksend
48 messages · Page 1 of 1 (latest)
What kind of provider is it?
Email?
No SMS
Communicate with your customers and staff via SMS, voice, email, rich media, direct mail and more with ClickSend United States. From single to scale by web app, API or integration.
Clicksend is a SMS provider and I use Elestio to host it
I found the way to get the custom provider
Is the sender number the one that sends the message or is it the one that the user owns?
SMS is not working
Its the Same API key and It does not work 😦
Failed sending to target [My Number] with error: Invalid credentials or this token has been revoked.
when clicksend is a copy and paste
sounds like a bad api key
When you initialize the appwrite SDK, you need to do .setKey() and specify a valid API key. The key is probably not valid
Pretty sure he’s referring to the Clicksend API key
Not setting the Appwrite API key would result in a very different error
Appwrite currently only supports Twilio, Textmagic, Telesign, MSG91 and Vonage for Messaging SMS
Also, you can use appwrite functions to use other providers, but you will need to write and handle the entire flow by yourself
ok
That could work for this use case but how could I write the flow for the cloud version
because I migrated from elestio to AppWrite
You’d build the sending login in an Appwrite Function, and then you could call that Function from your code
could we be on a email chain for that?
I’m not sure what you mean by that?
Like on like a email then reply to each others questions?
Instead of this?
What would be the advantage?
company emails are ETE
also How could I connect clicksend using functions
SDK NOT ADDED
x-xcode-log://EE357E25-66BD-4DB3-BB48-2ED8719F5864 Revision 4f54f6255d0981887f0284aef7d6d85bd61016c6 for sdk-for-apple remoteSourceControl https://github.com/appwrite/sdk-for-apple version 7.0.0 does not match previously recorded value 3231f9b89bd57f02edf77d49ca9031d4741e0425
What's this?
Tried getting the package from a server to a app local package
to store it locally
hey @midnight hamlet I tried removing derived data and clearing out the swift package cache, but still get the same issue. The only thing that works for me is specifying an exact commit.
I'm trying to understand where this issue would propogate locally, unless there is some middle layer. or a bug in the new XCode.
@quick kettle have we validated the swift package works on a blank project in the new XCode? The fact this is happening for 2 folks, likley could point towards more.
even tried to clean the package locally.
yeah it is like that
That is very strange
Is there any update on this
@midnight hamlet @dense fossil This looks like a cache issue because of a bad release of 7.0.0. From Xcode, try File > Package > Reset Package Caches. If you've already tried this with no success, try to remove and re-add the package. Works okay in a fresh project
will try tomorrow. but for reference i had deleted every cache under the sun.
Ok
It did not work 😦 and I was off sick but back but it did not work
Showing All Issues
Revision 4f54f6255d0981887f0284aef7d6d85bd61016c6 for sdk-for-apple remoteSourceControl https://github.com/appwrite/sdk-for-apple version 7.0.0 does not match previously recorded value 3231f9b89bd57f02edf77d49ca9031d4741e0425
Very strange, you could try to manually update the lock file if nothing else is working. Should be found in [your app].xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved
Look for the sdk-for-apple block and make sure it looks like this (probably need to replace the revision with the one here)
{
"identity" : "sdk-for-apple",
"kind" : "remoteSourceControl",
"location" : "https://github.com/appwrite/sdk-for-apple",
"state" : {
"revision" : "4f54f6255d0981887f0284aef7d6d85bd61016c6",
"version" : "7.0.0"
}
},
After that you'll need to run "Update to latest package version" from Xcode again