After changing wifi networks, exporter doesn't work anymore[BUG]

[Hendrxxx666]

Hi,

I've been using SWEX for a while now, sometimes when i'm at work but since we switched offices (and thus, wifi networks), i seem to have been unable to export my JSON file. I still use the same desktop with SWEX on it, firewall allows SWEX, the IP/port is correct but everytime i start the proxy and then load up the SW app, the screen stays black for a while and then says "Failed to connect with the network. Please try again later.". Do you have any experience with this and/or a fix?

Thanks in advance

[Xzandro]

Sadly I dont have any experience with this and I pretty much only haver one Wifi network. So if someone else wants to look into that I wouldn't mind.

[HamzaLodhi]

I just moved to a new house too where my neighbour's internet is hot garbage. I spent too much time figuring out how to make it work. Eventually I tried the 0.0.27 version of summoners war exporter, and it actually worked! You should definitely try it out and see if it works for you.

[Xzandro]

I would not recommend this. 0.0.27 has only a HTTPS mode, nothing else. Newest versions can both via the HTTPS mode option in the settings. This issue is NOT related to the HTTPS switch of com2us.

[Celteron]

Maybe iam right here. I want to use SWEX to get the JSON file. Last usage was in december or november. When iam starting the proxy all is fine, tipping the right Port and IP in my mobile phone. Start SW and it works, but the Export doesnt create a JSON. If iam enabling HTTPS Mode -> SW has connection problems. I dunno what I can do to fix that. Used Version 0.0.37 and 0.0.35 and 0.0.23

[Xzandro]

You are not. Please don't use this issue for help regarding the new (old) HTTPS steps or I will lock this issue.

[deirdresm]

I'm not sure this issue is related to the wifi network (though I also have one that's hot garbage).

I'm not getting profile exports (or any data exports) since 0.0.37 came out, and my swarfarm also hasn't been updating. I've just been too busy with other things to have noticed.

Note that I'm on macOS, though that hasn't been the issue in the past.

I can get the app to manually write a cert, so I know it has write permission.

[deirdresm]

To give a clearer description of what's happening:

1. I tried the given release, then hand-built another with npm install followed by npm run dist (as I'm a registered dev).

2. I have enabled every single plugin that's default.

3. I made sure I'm proxying through the app as per usual, then restarted SW and played for a few.

4. Nothing shows in the Logs screen, no files written to disk.

[Xzandro]

This is also not relevant to this issue. Its because of com2us's reactivation of HTTPS, as described in the countless closed issues here. See #359 Really thinking about locking this issue for now, so people don't derail / confuse this with the HTTPS issue and not understanding that they need additional steps again now.

This might a valid real issue or bug, but this has nothing to do with the current HTTPS situation.

[deirdresm]

Apologies for the noise then, and thank you.

Perhaps a small line on the top of the README would help avoid more dups?

[Xzandro]

Perhaps. When I look at most of these issues, I kinda doubt that people would actually read this first tho. :/

[deirdresm]

The root of my issue appears to be more fundamental: there is no httpsMode checkbox on the macOS version. I can set it manually, I'd guess, but that's likely the root of the issue: can't check a checkbox that doesn't exist.

[Xzandro]

You might want to create a new issue for that. I don't see how this can be missing tho, since this is not OS specififc and is definitely in the newest code. https://github.com/Xzandro/sw-exporter/blob/4a4315711b6b411718af29678f620b6caf959941/app/pages/Settings.js#L80

Lets not go into it in this issue tho.

[nessoaf]

Hey, possible new bug, a friend and I both tried to get a JSON tonight (15 min ago) on each of our accounts and neither of us are able to. It was working previously. Either new update (thank you by the way you are awesome) or the new SW update/http(s) issues has arisen. Hope this is of some help.

[Xzandro]

Okay, will lock this issue now. At this point this is just a dumpster fire of an issue for people, who don't udnerstand that they need a additional steps because of HTTPS, See #359

Might reopen in a few weeks.