Rule Builder iOS app

Ok, so then that should show up under “Which switches?” during login, then in with all of the other switches in the triggers. Do you see it in those two places?

Ahh, that was the problem, I hadn’t selected it under switches. All good now!

1 Like

Anybody having issues using this app after the platform update today?
It wasn’t working so I logged out and now it won’t complete the sign in.
After I press Authorize it just sits at white screen with Blue circle that spins for ever.

I just tried this and noticed some issues too. I’ve also noticed that doing anything in the IDE is sometimes requiring refreshing the page before anything shows up, so this may be related to the issue. Let’s see if it resolves itself, otherwise, I’ll dig deeper.

:grinning: yes I noticed that refresh issue as well.
At least I’m not going crazy.

I was getting the same issue in the IDE but it resolved itself.

When you get some time I thought I would let you know I still can’t get into the application. I noticed that it adds the smart app to the Convenience group but the app no longer goes past the white post authorization screen.

Thanks for all of your help

I’m seeing the same and am looking into it now. I’ll post an update once I figure something out.

I’m not being pushy just curious if you found anything yet

SmartThings support has confirmed that there are a couple of platform wide issues which affect Oauth that they are working on fixing. We’ll have to wait until they resolve these.

And yet status.smartthings.com has not been updated yet. Ugh. I’ve noticed this more lately where they are not updating the status site when there are platform issues.

2 Likes

I realize we are using custom smart apps and can’t expect them (ST) to worry about the expect that there updates have. but they should offer some sort of beta test for their platform updates. Or make an announcement that there is an upgrade occurring and these are the changes they may affect your apps. It seems like things are crap and barely work and It’s really starting to piss me off. The iOS app runs worse than it even has now and I have to constantly tinker with crap to figure out why it might not have worked like it should.
I guess the one positive is that all of the devices I have installed are industry standard z-wave devices so I will work with any future controller that supports z-wave. All i know is I was so excited about this platform and now it’s losing it’s appeal and now my wife has become irritated by its inconsistencies. The only reason i am sticking it out is because of the awesome developer community here. It certainly isn’t because of the feeling of ST’s dedication to the platform. Sorry for highjacking your thread for my rant. I’m just irritated and needed to vent.

2 Likes

just bought this app but every time i try to authorize it just shows a blue spinning circle. waited 15 minutes then gave up. any ideas?

just read the previous post that say there is currently an issue… 4 days ago… this still going on?

Yes, unfortunately the problem is sill there. SmartThings support has told me that they have a server update going out on Monday which should fix everything. We’ll have to wait and see.

@obycode Hey – I was wondering if there was a way to manually allow access to the app (maybe by adding a custom smart app?). I am eager to use this great and very helpful app.
Thanks!

Yes, I think this could be possible, where we could generate the token in the SmartApp, and then enter it manually into the app. The problem though is that this will require an update to the app which means if we can do it, we would still have to wait 10 days or so to go through Apple’s approval process. If it isn’t resolved tomorrow, we’ll begin investigating this option.

Any news @obycode?
I had a phone swapped, restored from backup, and now I can’t log into SmartRules because of this crazy issue.
I know its not your fault, but it’s still frustrating.

I’m told that they did push some update today, but I’m still seeing the same issue. Still waiting to hear more. And yes, it is very frustrating!

Thanks for keeping us in the loop. Your dedication to supporting your app is a rare thing and it’s much appreciated.
I have noticed that the app now crashes after pressing authorize button now.
Looking at the logs on my phone i see:

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000048
Triggered by Thread:  3

Filtered syslog:
None found

Thread 0 name:  Dispatch queue: com.apple.main-thread
Thread 0:
0  libsystem_kernel.dylib        0x0000000199bb8910 0x199bb8000 + 2320
1  libsystem_kernel.dylib        0x0000000199bb8788 0x199bb8000 + 1928
2  CoreFoundation                0x0000000184b8a8d0 0x184aac000 + 911568
3  CoreFoundation                0x0000000184b885a8 0x184aac000 + 902568
4  CoreFoundation                0x0000000184ab50cc 0x184aac000 + 37068
5  GraphicsServices              0x000000018fa2f16c 0x18fa24000 + 45420
6  UIKit                        0x000000018a1c65ec 0x18a14c000 + 501228
7  SmartRules                    0x0000000100132eec 0x1000c4000 + 454380
8  libdyld.dylib                0x0000000199ab68b4 0x199ab4000 + 10420

Thread 1 name:  Dispatch queue: com.apple.libdispatch-manager
Thread 1:
0  libsystem_kernel.dylib        0x0000000199bd459c 0x199bb8000 + 116124
1  libdispatch.dylib            0x0000000199a98a18 0x199a84000 + 84504
2  libdispatch.dylib            0x0000000199a87cb0 0x199a84000 + 15536

Thread 2:
0  libsystem_kernel.dylib        0x0000000199bd3c0c 0x199bb8000 + 113676
1  libsystem_pthread.dylib      0x0000000199c90f54 0x199c90000 + 3924
2  libsystem_pthread.dylib      0x0000000199c90a44 0x199c90000 + 2628

Thread 3 name:  Dispatch queue: com.apple.NSURLSession-work
Thread 3 Crashed:
0  CFNetwork                    0x00000001842ee308 0x1842b8000 + 221960
1  CFNetwork                    0x00000001842ee304 0x1842b8000 + 221956
2  CFNetwork                    0x000000018435938c 0x1842b8000 + 660364
3  CFNetwork                    0x000000018435c594 0x1842b8000 + 673172
4  CFNetwork                    0x000000018435d9e0 0x1842b8000 + 678368
5  CFNetwork                    0x00000001843d6de8 0x1842b8000 + 1175016
6  CFNetwork                    0x000000018435d3b4 0x1842b8000 + 676788
7  libdispatch.dylib            0x0000000199a85a04 0x199a84000 + 6660
8  libdispatch.dylib            0x0000000199a859c4 0x199a84000 + 6596
9  libdispatch.dylib            0x0000000199a916dc 0x199a84000 + 55004
10  libdispatch.dylib            0x0000000199a8907c 0x199a84000 + 20604
11  libdispatch.dylib            0x0000000199a93718 0x199a84000 + 63256
12  libdispatch.dylib            0x0000000199a93050 0x199a84000 + 61520
13  libsystem_pthread.dylib      0x0000000199c90e94 0x199c90000 + 3732
14  libsystem_pthread.dylib      0x0000000199c90a44 0x199c90000 + 2628

Interesting, I haven’t seen any crashes, just the hanging, but I’ll look into it. Can you send me the full crash log via email?