Troubleshooting

@questionsforever We had a new update, which should have fixed the issue. Is it working for you now?