Hi everyone,
I’m aware that some of you have experienced difficulties with the Trongate Desktop App. After looking into it, it appears there are a few different issues happening at the same time. I’ll send a more detailed report shortly. In the meantime, if you need to use the Trongate Desktop App, I recommend switching to the Node.js version.
HOW TO GET THE NODE.JS VERSION
You can download the Node.js version of the Trongate Desktop App from: https://github.com/trongate/trongate-desktop-app
There are some really useful instructions on the page - be sure to check it out and let me know if you run into any difficulties.
FIX EXPECTATION
I expect to have the full fix completed by midnight on Sunday/Monday. I’ll keep you updated on any developments here on this thread.
Desktop App Issues
9 months ago
9 months ago
#1
9 months ago
#2
Hi David, I just created a new module to an existing app. This is the Manage file created
You can see after the searchphrase line there is missing code. The $params and $sql.
There are 2 timestamp fields, created_at and updated_at missing
Dan
You can see after the searchphrase line there is missing code. The $params and $sql.
There are 2 timestamp fields, created_at and updated_at missing
Dan
9 months ago
#3
Hi DC, well spotted! I was on node version 20.9.0, so dropped it down to 18.17.1 with this commandcloned the desktop app withthen ranThe Desktop app ran, I then created a new app and modified an old one with no problems 😉
Those instructions I put in the README.md came in handy. I tried it again with the latest version of Electron (37.2.3) and Node (22.17.0), but it failed.
I see there were a few warnings when `npm install` rancould be due to the outdated dependencies in `package.json` and then their dependencies and so on...
A dependency nightmare!but assume you already knew that.
If you see me online in Teams, give me a shout and I might be around for a chat.
Those instructions I put in the README.md came in handy. I tried it again with the latest version of Electron (37.2.3) and Node (22.17.0), but it failed.
I see there were a few warnings when `npm install` rancould be due to the outdated dependencies in `package.json` and then their dependencies and so on...
A dependency nightmare!but assume you already knew that.
If you see me online in Teams, give me a shout and I might be around for a chat.
9 months ago
#4
Yikes!
Looks like I'm having one of those beautiful moments where loads of things go wrong at once.
I noticed a critical fault yesterday with the post() function. If you added a UK phone number such as '01412345432', the post function would remove the leading 0!
This has nothing to do with the desktop app but it's obviously a fairy critical thing. I've spent some time working on that and it has now been pushed out. So, we have a beautiful new post() function.
As for the desktop app?
Looks like it's problems stacked on top of problems. I had no issue getting it to work with Node but perhaps I was just lucky.
Now that I have the post() function fixed, let me spend a little time working on the desktop app issue(s). Simon, I appreciate your offer to meet up on Teams and I would absolutely like to do that. Right now, however, I'm a bungling idiot with regards to this problem. Grant me a little bit of time to play around with this so that when I meet up with you, I'll be ready.
Life is good. I always win. I never lose. I'm really lucky.
Ahoy!
Looks like I'm having one of those beautiful moments where loads of things go wrong at once.
I noticed a critical fault yesterday with the post() function. If you added a UK phone number such as '01412345432', the post function would remove the leading 0!
This has nothing to do with the desktop app but it's obviously a fairy critical thing. I've spent some time working on that and it has now been pushed out. So, we have a beautiful new post() function.
As for the desktop app?
Looks like it's problems stacked on top of problems. I had no issue getting it to work with Node but perhaps I was just lucky.
Now that I have the post() function fixed, let me spend a little time working on the desktop app issue(s). Simon, I appreciate your offer to meet up on Teams and I would absolutely like to do that. Right now, however, I'm a bungling idiot with regards to this problem. Grant me a little bit of time to play around with this so that when I meet up with you, I'll be ready.
Life is good. I always win. I never lose. I'm really lucky.
Ahoy!
9 months ago
#5
Just for clarity can I please ask you folks to give me a clear 'aye' or 'naw' for the following questions:
1). Did you have difficulty installing the Trongate Desktop App using Node.js?
2). Regardless of whether or not you had difficulty, did you get it up and running (with Node.js) eventually?
3). Are you able to work with the Node.js version of the Desktop App, for now?
1). Did you have difficulty installing the Trongate Desktop App using Node.js?
2). Regardless of whether or not you had difficulty, did you get it up and running (with Node.js) eventually?
3). Are you able to work with the Node.js version of the Desktop App, for now?
9 months ago
#6
Hi Dan,
Thanks for taking the time to post.
Just to clarify - when you said, "This is the Manage file created", I wasn’t entirely sure which file you were referring to. The manage.php file is a view file, and on my end, it looks like this:
Alternatively, perhaps you meant the manage method within the controller? Here’s what I’m seeing for that:
I’m keen to help, but it would really help me (and others too) if bug reports could be as specific as possible. Even a small amount of extra detail can save hours - sometimes even days - of back-and-forth.
I completely understand things can get rushed sometimes, but when reporting an issue, any extra context you can give will really help us troubleshoot quickly and effectively.
Much appreciated, and thanks again for raising this.
Thanks for taking the time to post.
Just to clarify - when you said, "This is the Manage file created", I wasn’t entirely sure which file you were referring to. The manage.php file is a view file, and on my end, it looks like this:
Alternatively, perhaps you meant the manage method within the controller? Here’s what I’m seeing for that:
I’m keen to help, but it would really help me (and others too) if bug reports could be as specific as possible. Even a small amount of extra detail can save hours - sometimes even days - of back-and-forth.
I completely understand things can get rushed sometimes, but when reporting an issue, any extra context you can give will really help us troubleshoot quickly and effectively.
Much appreciated, and thanks again for raising this.