Problems with builds #96

Open
opened 2025-06-09 17:27:47 +08:00 by sebaxakerhtc · 7 comments
sebaxakerhtc commented 2025-06-09 17:27:47 +08:00 (Migrated from github.com)

Hi. Awezome project, but here are problems I'm facing:

  • MSI windows packege is never compiled because of errors.

  • EXE windows packege not work with CMD installation arguments, like --silent-install or --install when I use hide-help-cards=Y
    Image
    When I run myapp.exe --install | more I see skip .\files_to_be_installed
    So, I should rebuild my apps without hide-help-cards=Y and then --install and --silent-install work again

  • MacOS builds doesn't start with error of broken code (I have sudo spctl --master-disable and open it with ctrl+click => open)

Hi. Awezome project, but here are problems I'm facing: - MSI windows packege is never compiled because of errors. - EXE windows packege not work with CMD installation arguments, like --silent-install or --install when I use `hide-help-cards=Y` ![Image](https://github.com/user-attachments/assets/2415776b-b49a-4c26-b424-df7b0a2b2657) When I run `myapp.exe --install | more` I see `skip .\files_to_be_installed` So, I should rebuild my apps without `hide-help-cards=Y` and then `--install` and `--silent-install` work again - MacOS builds doesn't start with error of broken code (I have `sudo spctl --master-disable` and open it with ctrl+click => open)
bryangerlach commented 2025-06-10 03:24:22 +08:00 (Migrated from github.com)

The MSI build will fail if the app name used has any special characters or non-English characters I believe.

I can look into the issue with CMD arguments not working, I have no idea about that though.

I do not have any Apple products to test anything on, so I'm not sure what the issue might be. Most of the mac stuff was contributed by another user here. I can try and figure out what is going wrong.

The MSI build will fail if the app name used has any special characters or non-English characters I believe. I can look into the issue with CMD arguments not working, I have no idea about that though. I do not have any Apple products to test anything on, so I'm not sure what the issue might be. Most of the mac stuff was contributed by another user here. I can try and figure out what is going wrong.
sebaxakerhtc commented 2025-06-10 03:35:04 +08:00 (Migrated from github.com)

The MSI build will fail if the app name used has any special characters or non-English characters I believe.

Thx for your fast reply!
There's no any special characters or non-English characters. Just like MyAppName

I can look into the issue with CMD arguments not working, I have no idea about that though.

Looks like my bad - that happens only on Win7

I do not have any Apple products to test anything on, so I'm not sure what the issue might be. Most of the mac stuff was contributed by another user here. I can try and figure out what is going wrong.

That's nice! I have M1 and Macbook and Intel Mac - so I can test. For now I'm using an original RustDesk with settings pointing to my server.

And one more question:
This option Allow hiding the connection window from remote screen does nothing :(
I was thinking the problem is in API server, - so I installed your API server, but with no luck.
Any suggestions?

> The MSI build will fail if the app name used has any special characters or non-English characters I believe. Thx for your fast reply! There's no any special characters or non-English characters. Just like `MyAppName` > I can look into the issue with CMD arguments not working, I have no idea about that though. Looks like my bad - that happens only on Win7 > I do not have any Apple products to test anything on, so I'm not sure what the issue might be. Most of the mac stuff was contributed by another user here. I can try and figure out what is going wrong. That's nice! I have M1 and Macbook and Intel Mac - so I can test. For now I'm using an original RustDesk with settings pointing to my server. And one more question: This option `Allow hiding the connection window from remote screen` does nothing :( I was thinking the problem is in API server, - so I installed your API server, but with no luck. Any suggestions?
bryangerlach commented 2025-06-10 03:39:29 +08:00 (Migrated from github.com)

I have not tested the hide connection window feature, but I know that you have to have a permanent password set, and the Password Approve mode has to be set to "Accept sessions via password". I can look into the issue.

I have not tested the hide connection window feature, but I know that you have to have a permanent password set, and the Password Approve mode has to be set to "Accept sessions via password". I can look into the issue.
sebaxakerhtc commented 2025-06-10 04:00:34 +08:00 (Migrated from github.com)

I have not tested the hide connection window feature, but I know that you have to have a permanent password set, and the Password Approve mode has to be set to "Accept sessions via password". I can look into the issue.

Yeah, I read about that and setted up all like that, "Accept sessions via password" and permanent password...
Let me know about your tests. Thx

I think something wrong...
I have this
Image
but on client side there's still window to allow connection with click

> I have not tested the hide connection window feature, but I know that you have to have a permanent password set, and the Password Approve mode has to be set to "Accept sessions via password". I can look into the issue. Yeah, I read about that and setted up all like that, "Accept sessions via password" and permanent password... Let me know about your tests. Thx I think something wrong... I have this ![Image](https://github.com/user-attachments/assets/704c7c12-d59a-4e39-b071-77aa73977233) but on client side there's still window to allow connection with click
sebaxakerhtc commented 2025-06-11 01:09:38 +08:00 (Migrated from github.com)

Hey!

I found that "hide connection window feature" was only 1.2.0 - 1.2.2 versions.
After that it can be setted up only in Pro version (by API server). Or maybe you can add this functionality at your API server?
🥇

So...
Two questions:
1) Can you add 1.2.2 to versions list
2) Can you add support for x86 builds for Windows like rustdesk official builds? (They uses sciter if I understand correctly)
Maybe you can add a checkboxes about versions? If anybody want to build x86 only, exe only, msi only, all of them...
This will save the time of building.

Btw, MSI builded on 1.4.0, but not on nightly
Best regards!

Hey! ~~I found that "hide connection window feature" was only 1.2.0 - 1.2.2 versions. After that it can be setted up only in Pro version (by API server). Or maybe you can add this functionality at your API server?~~ 🥇 So... ~~Two questions:~~ ~~1) Can you add 1.2.2 to versions list~~ 2) Can you add support for x86 builds for Windows like rustdesk official builds? (They uses sciter if I understand correctly) Maybe you can add a checkboxes about versions? If anybody want to build x86 only, exe only, msi only, all of them... This will save the time of building. Btw, MSI builded on 1.4.0, but not on nightly Best regards!
sebaxakerhtc commented 2025-06-12 02:33:52 +08:00 (Migrated from github.com)

Hey there!

Today I tested your Allow hiding the connection window from remote screen. and it WORKS!
My mistake - to try it on nightly - it doesn't work like MSI package.

BUT!!!
If I set Allow hiding the connection window from remote screen. it add in menu this option, but it's DISABLED by default.
And I want to Disable Settings for end user (client).
Can you do that enabled by default if Allow hiding the connection window from remote screen. is checked?

I'll donate you this month, I promise! I really love your project! (look at your API server project issues about user icons - that matters)

THANK YOU!

Hey there! Today I tested your `Allow hiding the connection window from remote screen.` and it WORKS! My mistake - to try it on nightly - it doesn't work like MSI package. BUT!!! If I set `Allow hiding the connection window from remote screen.` it add in menu this option, but it's DISABLED by default. And I want to `Disable Settings` for end user (client). Can you do that enabled by default if `Allow hiding the connection window from remote screen.` is checked? I'll donate you this month, I promise! I really love your project! (look at your API server project issues about user icons - that matters) THANK YOU!
hdlineage commented 2025-06-28 08:03:40 +08:00 (Migrated from github.com)

The MSI build fails with master branch because nuget doesn't accept master as version number.
To fix, just override the version environment variable during the build step:

$env:VERSION = "1.4.0"
nuget restore msi.sln

The MSI build fails with master branch because nuget doesn't accept master as version number. To fix, just override the version environment variable during the build step: $env:VERSION = "1.4.0" nuget restore msi.sln
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: 3344/rdgen#96