-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to upgrade 4.1.0 however 4.0.0 works fine #312
Comments
Just adding a little bit of additional troubleshooting information on this one as I ran into this a couple days ago. I believe this is happening because the directory structure after extracting the files from the nuget package winds up with file paths that exceed 260 characters which is the default maximum in Windows. This causes the files to not actually get created thus resulting in the "Could not find a part of the path" error you are getting. If you look in the location listed, the folder will contain files with shorter filenames but will be missing the file referenced and probably several others. I was able to work around this by moving my project closer to the drive's root directory, deleting the OneSignal package from the packages folder, and restoring the package. Since the paths will be shorter at this point, it all worked properly. This only affects Windows, as the max path length on Mac is much longer. |
I have moved my project to closer to drive root directory "deleting the OneSignal package from the packages folder, and restoring the package" Thank you |
Ahh, I forgot about that step. I wound up having to go in and remove the OneSignalSDK.Xamarin package from the global NuGet package folder on my computer as well. The file path length issue is unfortunately an issue there as well. I just went to the folder you listed above, found the OneSignalSDK.Xamarin folder and removed it. There is probably a better way to go about that, but that worked for me. As for steps, I closed Visual Studio, removed the package, and then restarted Visual Studio. Visual Studio automatically restored the package to the project's packages directory with the shorter directory path and it worked properly after that. This isn't really a good long term solution to this problem, and I'm sure there is probably a much better way to do this through the NuGet CLI, but these steps did work for me. |
I Have the same issue - and I could not upgrade to 4.10 to see if some other issues that exists on 4.0.0 were fixed. What changed between 4.0.0 and 4.10 @jkasten2 thanks |
This is how I have solved.
OR
Then do nuget restore, it basically install all the nuget packges to new location. now install OneSignalSDK.Xamarin Thanks @ChrisMonson for helping me out |
@Dipannita20 thank you for your time and reply. `
I have added
Missing the obvious? |
@Dipannita20 yep managed to make it work as you suggested - now 4.1.0 installs however I still get Severity Code Description Project File Line Suppression State and I dont get that at all with V3 or V4.0.. Any ideas anyone |
Description:
(your description here)
Environment
Visual Studio 2019 Professional windows
Steps to Reproduce Issue:
Package not installing getting below error, attached exception
Anything else:
onesignal_4.1.0_upgrade_exception.txt
n here)
The text was updated successfully, but these errors were encountered: