#Clicksend

48 messages · Page 1 of 1 (latest)

midnight hamlet
#

Hi all, Is there a way to connect Clicksend as a provider

olive wasp
#

Email?

midnight hamlet
#

No SMS

midnight hamlet
#

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?

midnight hamlet
#

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

midnight hamlet
#

Wdym

#

When I use the PHP lib it works but with AppWrite it doesnt

olive wasp
foggy inlet
#

Not setting the Appwrite API key would result in a very different error

foggy inlet
olive wasp
#

Also, you can use appwrite functions to use other providers, but you will need to write and handle the entire flow by yourself

midnight hamlet
#

ok

midnight hamlet
#

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

foggy inlet
midnight hamlet
#

could we be on a email chain for that?

foggy inlet
midnight hamlet
foggy inlet
#

What would be the advantage?

midnight hamlet
#

company emails are ETE

midnight hamlet
#

also How could I connect clicksend using functions

midnight hamlet
#

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

olive wasp
midnight hamlet
#

Tried getting the package from a server to a app local package

midnight hamlet
#

to store it locally

dense fossil
#

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.

midnight hamlet
#

yeah it is like that

midnight hamlet
#

Is there any update on this

quick kettle
#

@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

dense fossil
midnight hamlet
#

Ok

midnight hamlet
midnight hamlet
#

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

quick kettle
# midnight hamlet Showing All Issues Revision 4f54f6255d0981887f0284aef7d6d85bd61016c6 for sdk-for...

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

midnight hamlet
#

I'm using the app Playground to develop the app

#

@quick kettle