Block Market V1.1.1. Stuck on loading screen

[Madland12]

I loaded Block Market version 1.1.1. and it worked for about 2 hours. Now it gets stuck on the Loading Screen. Is there a fix for this condition. I am running Windows 10 operating system.

[peteralexander25]

did you fix this?

[Madland12]

No I have not resolved this. I can not recover my original Wallet. The only place I can see my original Wallet address is on Changelly in my transaction history. I tried to back up my original Wallet and install It in my new wallet and it said the transfer could not nlbe completed due to a error. I am not sure what else to do. I am not sure that the wallet back up I had was even a good back up.

…

On Nov 27, 2017 7:57 PM, "peteralexander25" ***@***.***> wrote: did you fix this? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#267 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AgRig8S4YjvzUi9YHrxUPGSfH3sVlwj9ks5s61qDgaJpZM4QkqBl> .

[peteralexander25]

No I have not I get this error message is there a way to take my token out and send to another wallet ? [image1.jpeg] On 28 Nov 2017, at 02:14, Madland12 <notifications@github.com<mailto:notifications@github.com>> wrote: No I have not resolved this. I can not recover my original Wallet. The only place I can see my original Wallet address is on Changelly in my transaction history. I tried to back up my original Wallet and install It in my new wallet and it said the transfer could not nlbe completed due to a error. I am not sure what else to do. I am not sure that the wallet back up I had was even a good back up.

On Nov 27, 2017 7:57 PM, "peteralexander25" ***@***.******@***.***>> wrote: did you fix this? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#267 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AgRig8S4YjvzUi9YHrxUPGSfH3sVlwj9ks5s61qDgaJpZM4QkqBl> .

— You are receiving this because you commented. Reply to this email directly, view it on GitHub<#267 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AgeDkkBM1u4Xm2TRAeqSpZQNE5jtYBCyks5s62yFgaJpZM4QkqBl>.

[Madland12]

So is there a way I can download a new wallet and put my original Wallet address into it to transfer my coins? On Nov 28, 2017 5:16 AM, "peteralexander25" <notifications@github.com> wrote:

…

No I have not I get this error message is there a way to take my token out and send to another wallet ? [image1.jpeg] On 28 Nov 2017, at 02:14, Madland12 ***@***.***<mailto: ***@***.***>> wrote: No I have not resolved this. I can not recover my original Wallet. The only place I can see my original Wallet address is on Changelly in my transaction history. I tried to back up my original Wallet and install It in my new wallet and it said the transfer could not nlbe completed due to a error. I am not sure what else to do. I am not sure that the wallet back up I had was even a good back up. On Nov 27, 2017 7:57 PM, "peteralexander25" ***@***.***< ***@***.***>> wrote: > did you fix this? > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/syscoin/blockmarket-desktop-public/ issues/267#issuecomment-347378764>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/ AgRig8S4YjvzUi9YHrxUPGSfH3sVlwj9ks5s61qDgaJpZM4QkqBl> > . > — You are receiving this because you commented. Reply to this email directly, view it on GitHub<https://github.com/ syscoin/blockmarket-desktop-public#267#issuecomment-347391539>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ AgeDkkBM1u4Xm2TRAeqSpZQNE5jtYBCyks5s62yFgaJpZM4QkqBl>. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#267 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AgRig2G3Kk0WsJbOqfyu23i6WJG-MWXsks5s692UgaJpZM4QkqBl> .

[dwasyluk]

This is a duplicate of #264. Please continue the discussion there / track that issues progress to see when this is fixed. Currently slated for 1.1.3.