I think @hunterlester got this working recently - think he explained a bit on riot.
From memory I think you need to do your own build of SAFE Launcher with a flag for mock routing. The build process has been simplified recently so it’s probably easier than the instructions you’ll find on the forum, recent ones here I think:
Right now I’m compiling the dev branch of safe_browser which integrates Authenticator and the new DOM API.
I’ll get the binary up on the net for you to download since you are also on Windows.
My browser is up and running with authenticator management page, but now I need to figure out why it’s not successfully interfacing with leveldb, or whatever we are using as our local mock network.
Will, mock routing applies to anything built to access SAFE because it simulates the routing /storage layer.
I mentioned Launcher because MutableData and Authenticator are not finished yet. But if you want to pay with the code that’s there I guess you can, but I don’t know what works and what doesn’t.
Hey is Auth Browser 0.2.1 still the most recent browser that offers Mock-Routing?
Or is there a way to get it on 0.3.0? And is there a reason to? Like 0.3.0 has any special features or updates that 0.2.1 doesn’t have, like breaking changes?
Basically: if I want to do offline development right now, what’s the best browser for me to go get?
can’t get any of the Hosting manager or email app working against 0.2.1, @Joseph_Meagher do you have any builds working offline?
I think offline mockrouting would be best for development, so you don’t end up running out of PUTS and invitations constantly, on TEST 17. Is anyone successfully doing this?
It just wasn’t released with the mock libs, it shouldnt affect the capability itself I’d think.
If you mean just via Github releases then yep thats just 0.2.1 of the browser. 0.3.0 only had the network version put out for TEST-17. However that can be run with the mock network too if someone is ok with doing a manual build of safe_client_libs at this tag for the mock feature and replacing them accordingly in the supplied browser 0.3.0 package.
i don’t have a build working offline as testnet 17 was relatively painless developing on for me although the upcoming official mock browser could be very handy and important if it lets you enter the port you want for requests
I wouldn’t expect any different behaviour between platforms. K give me a few mins(say 20) pls and I’ll see if I can get the windows mock version of the browser @ 0.3.0 built for you