Next Update Release

[bkjimena11]

When will the next update get released?

[vanshg]

Probably soon -- I just graduated and should have a little bit more free time to work on this now.

[bkjimena11]

Oh OK. Cool. How soon do you think will you be able to release an update? And will we be able to visual see what Google Assistant replies back when we ask it something?

[vanshg]

I am aiming for February. I completely revamped the project in the interest of making it feel like a more polished product. There are still some issues to be sorted out. However, if you build from source, you can use MacAssistant in a somewhat working state. And yes, you can already visually see what Google Assistant replies when you ask it something!

[bkjimena11]

I don't see what Google Assistant says when I ask it something.

[vanshg]

Are you building from source? Only that has it. The builds on the downloads page do not.

[bkjimena11]

Oh I see. Where can I download a version that lets me see when Google Assistant replies to my request? I am not a programmer.

[vanshg]

There is no download available right now. You have to build from source

[bkjimena11]

How do I do that if I don't know how to program?

[vanshg]

There's instructions in the README. No explicit programming required to get it working, just some setup.

[bkjimena11]

Where is the README?

[vanshg]

https://github.com/vanshg/MacAssistant/blob/master/README.md#build-instructions

[bkjimena11]

Where is the location of "./MacAssistant/Config/google_oauth.json" on my computer?

[vanshg]

The "." refers to wherever you downloaded the repo to

[bkjimena11]

So I can create a folder called Config since it doesn't exist yet?

[vanshg]

It should already exist. If your repo directory is called MacAssistant, then you can find the Config directory in MacAssistant/MacAssistant/Config

[bkjimena11]

When I open the contents for MacAssistant, I have a folder called Contents. Then inside that folder, I have folders called _Code Signature, Frameworks, MacOS & Resources. Also in that folder are files called Info.plist & PkgInfo.

[bkjimena11]

What is happening now?

[bkjimena11]

Can you help me, please?

[vanshg]

You need to modify the contents of the repository, not the app. Please clone the git repo and modify from there

[bkjimena11]

Oh ok. What do I need to do? Can you send me pictures of what I should do?

[bkjimena11]

And where do you live? I live in Ottawa, Ontario, Canada and it is 2:26 AM here.

[vanshg]

Git clone the repository, follow the directions in the README to get the Google OAuth credentials, and follow the build instructions in the README

[bkjimena11]

I already got the Google OAuth credentials, how do I git clone the repository?

[domenicoblanco]

You have to install brew for macOS and then you could insert this command in your terminal git clone https://github.com/vanshg/MacAssistant.git

[bkjimena11]

I have installed brew and put in the command git clone https://github.com/vanshg/MacAssistant.git in the terminal, what is the next step?

[domenicoblanco]

You have to open the Finder and go to your users folder, open MacAssistant folder and open again MacAssistant folder, at this point, you should see a folder called Config, copy here your oauth token and change the name to google_oauth

[bkjimena11]

I do not see a folder called Config. I downloaded the 0.2 Soure.zip file. Is that right?

[domenicoblanco]

You should delete the zip and use the version downloaded from Git, the default folder is /Users/YourUsername/MacAssistant Edit: Also this is a year and an half old release

[bkjimena11]

How do I run the program now?

[domenicoblanco]

In order to run the program, you have to download xCode from the Mac App Store and run it once (to download some components) and then you have to navigate again inside the same folder in which there is the Config folder (/Users/YourUsername/MacAssistant) and open MacAssistant.xcworkspace. Once xCode loaded the project you can simply press the play button. To convert the project to a .app program, you have to go under Product → Archive and archive the app.

[bkjimena11]

Is there a way to check for updates automatically?

[domenicoblanco]

Not atm, this is a pre-release version. I suggest you to come and check. I've this repository on my favorites and check it at least twice a week.

[bkjimena11]

Is an archive called BoringSSL supposed to be made?

[domenicoblanco]

If I'm not wrong, it's one of the dependecies of this project so, it's normal

[bkjimena11]

This is what I am stuck on now, what do I need to do?

[domenicoblanco]

You're trying to export a dependency. You have to come back to xCode, select MacAssistant and archive it. Next you have to click Distribute Content into a local app

[bkjimena11]

Is it the first MacAssistant folder that I archive or the other folder named "MacAssistant " inside the first folder?

[vanshg]

Are you able to run it at all from Xcode (You can run it by hitting Command-R)

[bkjimena11]

What do you mean vanshg?

[bkjimena11]

Which file do I need to open in Xcode?

[bkjimena11]

When I open MacAssistant.xcworkspace, I press the play button. Then after that I press the archive option under product, then this is when the boringssl thing that I mentioned in other messages appears. I really don't understand what I should be doing. Can someone give a step by step guide on how I should be doing this?

[domenicoblanco]

When you run it, does it works?

[bkjimena11]

It does 133 tasks when I press the play button, is that right?

[domenicoblanco]

I'm not sure about the number of tasks but it should be right. What I mean is if you're able to use MacAssistant running it from the play button

[bkjimena11]

No.

[domenicoblanco]

In this case, there's an error during the building of the project. Are you able to see any error?

[bkjimena11]

I will show you what happens.

[bkjimena11]

It works now.