-
-
Notifications
You must be signed in to change notification settings - Fork 16
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
Certificate is not valid. #12
Comments
Thank you for reporting, where did you get the qownnotesapi? |
Thank you for the screenshot, but again: where did you get qownnotesapi? from the Nextcloud store? |
It's basically the same with pbek/nextbackup#18... |
update: So I download it from the NC store and will it be OK? |
Maybe this is of some help: nextcloud/server#4765 |
So I deleted and reinstalled as instructed on nextcloud/server#4765 (comment) (issuecomment-300181935) and you write this error anyway so maybe an NC server error |
App store returns badly signed archives |
@pbek I know where the bug is! The bug is in your application. A purely installed cloud, and the only allowed application ownbackup reports this error when you go into the additional settings Could not resolve AppName! Class AppName does not exist
|
How could it be a bug in the application if nothing was changed and it works in NC 11? |
@pbek Look at https://docs.nextcloud.com/server/12/developer_manual/app/settings.html https://github.com/pbek/ownbackup/blob/develop/appinfo/routes.php#L19 ['name' => 'admin#do_restore_tables', 'url' => '/restore-tables', 'verb' => 'POST'] It should be something like ['name' => 'settings#admin', 'url' => '/settings', 'verb' => 'POST'] There is some change. I did not study it very much, but I looked into other applications as it solves to write information to settings and do it differently. Look |
thank you for your research, @Laupe |
@Laupe I guess your comment about the routes was meant for ownbackup, right? qownnotesapi has no admin page... |
Can you please create an issue for that... |
But I still have no clue what is causing the |
@pbek Yes it was on ownbackup - Regarding the problem of ownbackup I will write in the issue you sent OC\IntegrityCheck\Exceptions\InvalidSignatureException |
You don't get "badly signed" applications into the NC store and why does it work on NC 11 and below... |
I see the same with Nextcloud 12 stable ...
|
Yes, it's not 100% what needs to be done in the future. Please see: nextcloud/server#4852 |
I can confirm this on Nextcloud 12 with the App installed from the Nextcloud store. |
I now released a new version of the app into the NC store that was signed with a NC certificate. Does that work for you? (You will have to reinstall the app.) |
@pbek I confirm, just reinstall the application (Disable, Delete, Install again from the app store) and all is fine! Thanks for the resolution. |
Works for me as well! Thanks.Best regardsDaniel HanssonTech and MeSent from mobile, sorry for typos.Den 23 maj 2017 4:48 em skrev Pavel Dvořák <notifications@github.com>:@pbek I confirm, just reinstall the application (Disable, Delete, Install again from the app store) and all is fine! Thanks for the resolution.
—You are receiving this because you commented.Reply to this email directly, view it on GitHub, or mute the thread.
|
Great, thank you for testing! |
Disabled, deleted, downloaded nc app store version. Download from nc app store: Disabled, deleted and installed via git as stated in Administrator Documentation - does NOT work too. :-( Any Ideas? |
did you delete it directly in your filesystem on your server? maybe not everything was removed... |
I checked the apps directory between each try if everything is removed correctly - so yes, uninstall is working. ;-) |
Then I frankly have no idea. :/ |
@jpaechnatz maybe the last comment in #15 helps you |
Nextcloud 12
The text was updated successfully, but these errors were encountered: