I think it will be noticed that this is not the identical email address specified in the properties. Actually, I'm not the publisher of Lib, but I just want to make it accessible to Particle users.
It someone else has uploaded a library with the same name (even only private) you cannot upload a library with that same name.
You either need to rename your library or file a PR on the original contributors repository and hope itāll be merged and updated by him.
@Postler, if you can provide the exact library name (stated in library.properties) @rickkas7 may be able to look up who has already claimed that name.
Ingo, I do remember helping @hasanals with the Pixy2 library a while back. Maybe he has claimed the library name but didnāt get round to publishing the lib.
But I canāt be sure as I have no access to the private libraries list.
No blanks in the library name! Thatās the reason why you see so many libraries with _ where youād normally use a blank. After all, the library name is also the name of the main .h and .cpp files and as such they mustnot contain blanks.
Since a blank breaks the library name, your ānewā name is still Pixy2.
Being the owner of the lib only depends on who - or rather which account - has uploaded a lib with that very name. There is no connection between the URL, Repository or Author field of library.properties.
I guess the error messages for your three tries did slightly vary, so it would have been good to state each of the individual responses too.
Try some other name again, but now right from the start with the name consistently set in library.properties, header .h and .cpp file. Maybe you were just āluckyā to again pick a name that was already taken.
Otherwise you can send me a zip file of your library and Iāll try to upload it.
Update:
After receiving @Postlerās zip file the reason for the issue became clear quite quickly. The library.properties file was invalid but the error message given by CLI was rather misleading.
After correcting the format of the file I was able to upload the library as Pixy2.
Currently the library hasnāt been made public.
At the moment I prepared the file-structure on a Windows-PC with renewing the lib.prop-file.
I wanted to upload, but I cant authenticate my login with a token.
On MacOS I get the question with e-mail, password AND Token (Pls enter a login code).
This is on Windows missing - using CLI v1.23.0.
Your CLI is rather old which most likely doesnāt support multifactor authentication.
Currently we are at 1.35.2
Try updating via particle update-cli and then try again.
There are 3 tools (boom, cryptiles, hoek) out of maintanance. Could be the problem?
Update: IĀ“m deleting CLI (npm uninstall -g particle-cli) and install the Windows-CLI by following this guide. Now v1.35.2 is available and login with token works.
Edited and successful uploaded as private library!
So where exactly do I find the private library to test before I share?
The documentation says that I could also access via WebIDE.
I can not find them now - too late for the eyes?