Windows 8.1 App Not Working Properly
Comments
-
Hi Mark - and welcome to the forums
Since upgrading my various Windows devices to Windows 8.1, the Logos "Metro" app does not work. In cannot access my preferred Bible version (NASB).
This probably doesn't relate to Windows 8.1 but to changes in the resources which render them incompatible with the app - see http://community.logos.com/forums/t/75840.aspx for a discussion of this. As Bradley (Logos) states they are still working out what to do about this
I love Logos 5 Desktop version, but would very much like to see additional development of the Metro app.
The last we heard from Logos is that there are no current plans to further develop this app
Graham
0 -
We hope to have a fix to the "Modern UI" Windows 8 app out soon. Sorry for the trouble.
0 -
Thanks, Bob !We hope to have a fix to the "Modern UI" Windows 8 app out soon. Sorry for the trouble.
Making Disciples! Logos Ecosystem = LogosMax on Microsoft Surface Pro 7 (Win11), Android app on tablet, FSB on iPhone & iPad mini, Proclaim (Proclaim Remote on Fire Tablet).
0 -
0
-
The updates to the Bible and Vyrso apps have been approved. After updating you should be able to view all your resources within the app. Please reply if you have any issues.
0 -
I had to uninstall Vyrso and reinstall on WIndows 8.1, but after that it works great. Thanks - Jim
0 -
Some of the resources will not open when downloaded onto my Surface RT. When I uninstall it and access it from the cloud, it will open. What's up with that??
0 -
Hi Mark
Some of the resources will not open when downloaded onto my Surface RT. When I uninstall it and access it from the cloud, it will open. What's up with that??
Which resources are you having problems with?
Graham
0 -
0
-
So far as I'm aware of are the commentaries by James Montgomery Boice
Sorry, I don't have those
Hopefully someone who does and has the Windows app will be able to check whether it works on their system to see if it is a general problem or something specific to your setup
0 -
This bug should be fixed in the latest release of the app. Thanks for the report!
0