[Bug]: Onesignal 5.1.5, 5.1.6 could not be resolved in iOS Swift Package Manager about onesignal-ios-sdk HOT 23 CLOSED

I am updating the release and tag in this repository, but anyone encountering this issue can use Package URL: https://github.com/OneSignal/OneSignal-XCFramework

from onesignal-ios-sdk.

same problem, for now will stick to 5.1.4

from onesignal-ios-sdk.

Have removed OneSignal-XCFramework-75c1bc28 & OneSignal-XCFramework-fe10aafb folders from ~/Library/Caches/org.swift.swiftpm/repositories
Now seeing this.
Still not able to add.

from onesignal-ios-sdk.

@nan-li using https://github.com/OneSignal/OneSignal-XCFramework resolved this issue for me and allowed me to install 5.1.6.

from onesignal-ios-sdk.

Hi @kunalzigma that's great to hear those commands worked! We just released Release 5.2.0 which includes a new feature for Push to Start Live Activities amongst other updates.

I'll close out this issue, feel free to @ me if you run into any problems.

from onesignal-ios-sdk.

Same problem with me. To fix it, I set the package to the exact version of 5.1.4.

from onesignal-ios-sdk.

HI @jenbitcoin and @djavan-bertrand, thank you for reporting.
We released version 5.1.6 recently and made an update to the files. Did you also clear SPMs package cache?

~/Library/Caches/org.swift.swiftpm/repositories

I am surprised version 5.1.5 is an issue for you as well. We released that version 2 weeks ago and made no changes to it.

from onesignal-ios-sdk.

Cannot add Sdk in new app.

from onesignal-ios-sdk.

Can reporters running into this confirm that removing ~/Library/Caches/org.swift.swiftpm/repositories did not work?

from onesignal-ios-sdk.

Apologies for the late reply, I have slow internet the past few days and updating SPM was such a nightmare and blocks me from doing my tasks. I'll try again today and see if 5.1.4 works.

As for the recent releases, I had cleared cache, removed derived data, deleted trash and it was not working. I also asked another teammate to update OneSignal to latest version and she encountered the same issue with me.

from onesignal-ios-sdk.

Hi,
We really had schedule of a major update for our app completed last week and release this week, and eagerly needed push notifications. We are able to add 5.1.5 with exact version. Done the testing, setup, and everything with 5.1.5. But really needed the 5.1.6 as we don't know when we will be updating the app next.
Similarly after the release of a newer 13 inch iPad, we will pushing updates to 3 other apps with onesignal.

So, we humbly request you to sort out this for us and others.

from onesignal-ios-sdk.

Hi everyone, I'm not sure why this is not working for people reporting. What xcode version are you using?

I am using xcode 15.2, and cleaning all my package caches was sufficient to add version 5.1.6.

We do plan to release 5.1.7 this week, but version 5.1.6 may also be added via commit: fc88833146e426eb4f64806baf5e494212458cad as it corresponds to its Release 5.1.6. Curious does this work?

from onesignal-ios-sdk.

Am on xcode 15.3 , and still same issue with adding that above SHA1 in commit. See the same as in the screenshot i provided before.

from onesignal-ios-sdk.

If 5.1.7 will be released this week, i can wait, but now the information is there, that this issue was happening with xcode 15.3. Hope that you take care of this with the new version.

from onesignal-ios-sdk.

I just tested with xcode 15.3, and was able to get the package.

Something with SPM is odd for some users, but I am not sure what... maybe some other configuration.

From the screenshots, the checksums indicate that SPM is returning an outdated / cached package for v5.1.6 as those are the old checksums. We updated the packages and checksums 7 days ago, so this downloaded package it is returning is over 7 days old.

The checksums we have currently are correct, and the correct packages are hosted, so I am not sure what we can do from our end.

EDIT to the above: ^ The only solution is we would have to make a new release.

SPM is grabbing the old packages and comparing the checksums to the current values.

from onesignal-ios-sdk.

I'm looking for similar issues online, can you try these steps?

• removed an old onesignal-xcframework
• chose 'Up to Next Major Version' for a new onesignal-xcframework
• deleted derived data folder
• rm -rf ~/Library/Caches/org.swift.swiftpm
• rm -rf ~/Library/Caches/com.apple.dt.*
• only after that tapped 'add package'

from onesignal-ios-sdk.

@nan-li On this commit, the command swift package resolve works, but on the previous one, it doesn't. It seems like it's trying to work with the commit that has a tag on it. Maybe this will help?

on 5.1.6 tag, checksum is specified as:

but in release it's different:

commit from first screenshot contains correct checksum:

from onesignal-ios-sdk.

Hmm @artem-tverdokhlebov, interesting,

I did not update that tag as the the Package.swift file for v5.1.6 of the onesignal-xcframework indicates to go to, for example:

https://github.com/OneSignal/OneSignal-iOS-SDK/releases/download/5.1.6/OneSignalFramework.xcframework.zip

And the correct zips with the correct checksums live there. SPM should just be downloading the assets that live on that release.

Ah. You know what.... just as I typed that.... I looked at screenshots again and realized users are adding the dependency via onesignal-ios-sdk?

Our ios setup instructions indicate to use Enter Package URL: https://github.com/OneSignal/OneSignal-XCFramework.

I did not realize users were adding it via this repository as well, which thinking about it, makes sense that people would do this.

from onesignal-ios-sdk.

As I look at the previous replies, I can see that users were clearly adding https://github.com/OneSignal/OneSignal-XCFramework, but still encountered this issue. However, it seems to be working now. Thanks, @nan-li!

from onesignal-ios-sdk.

I dont know what is going on. Seems like something is wrong.
The day 5.1.6 was released , i was easily able to add it one of my projects. A day later , same project wasnt even able to fetch the sdk. It seems it is available for a particular time and then it is not. Like something is controlling it.
Again, tried today right now , it didn't work. It might have been available when dfmuir & artem tried it because at that time, it was made available.
Anyways, I already waited too much for this from past 2-3 months and still no use. Seems a good time, to migrate to another push notification service. I made a mistake of waiting too much. In other cases, i never do that and remain in advantage.

from onesignal-ios-sdk.

And @nan-li , you can already in the screenshots, i was using the right url , the whole time. Even artem confirmed that.

from onesignal-ios-sdk.

Hi @kunalzigma I'm sorry you are experiencing such a headache.

I see some people such as the original poster do appear to be using OneSignal-iOS-SDK. I am not sure what issue you are running into. I downloaded 5.1.6 on the day it released in an example project, and then updated it the next day after we fixed some code signatures in the SDK. I ran into the checksum errors but running the following commands worked for me:

rm -rf ~/Library/Caches/org.swift.swiftpm
rm -rf ~/Library/org.swift.swiftpm
rm -rf ~/Library/Developer/Xcode/DerivedData

I read that rm -rf ~/Library/Caches/com.apple.dt.* is also a command that worked for some people.

Have you tried running all 4 of these commands together?

from onesignal-ios-sdk.

@nan-li the first 3 commands worked for me. I was able to get 5.1.6. Didnt need the 4th command. Thanks. Because 5.1.6 was performing great in one of our app added on 1st may , i needed it. But as you had announced 5.1.7 is around the corner, will be needing that too. Hopefully it comes out soon.

from onesignal-ios-sdk.