SmartThings Community

iOS 2.14.0 released (1/30/18)


(jkp) #8

No crashes but experiencing slowness loading things here and there with a couple of timeouts.


(Joel W) #9

I am on IOS and I just ordered my rooms. I opened a room and moved items around. Am I missing something?


(jkp) #10

rearranging and saving rooms works but when you open a room, rearrange items inside, click save, does it keep the order you rearranged them. For me, when I click save it goes back to alphabetical


(Joel W) #11

OK you got it right it lets you move, but doesn’t save when done.


(Brad) #12

The crashes seem to be isolated to iOS and custom device handlers.

We are looking into it but please reach out to support so we can track and follow up.


[RELEASE] Enhanced Wemo (Connect)
(Brad) #13

If iOS is crashing on 2.14.0, please check if you have an incorrect type set for a multiAttributeTile in a custom device handler. Here is an example of incorrect code

  tiles {
  	multiAttributeTile(name:"contact", type: "contact", width: 3, height: 2, canChangeIcon: true){
		tileAttribute ("device.contact", key: "PRIMARY_CONTROL") {
      		attributeState "open", label: '${name}', icon: "st.contact.contact.open", backgroundColor: "#ffa81e"
      		attributeState "closed", label: '${name}', icon: "st.contact.contact.closed", backgroundColor: "#79b821"
    	}
	}

Changing the ‘type’ from “contact” to “generic” should resolve the issue. We are also looking into fixing the app so it doesn’t crash with an incorrect type. On Android, this seems to manifest in a “?” tile.


Android app errors February 1, 2018
NEW: Aeon Home Energy Monitor v2 Device
Hub Firmware Release Notes - 20.17
[RELEASE] Life360 - Refreshed Every Minute & All Places & More UPDATED 01/01/2019 All API Data available for webCoRE Usage
SmartThings is a mess
(Neal B) #14

Count me in as one with crashing iOS app. I’ve opened a support ticket.

Is it just the “contact” type that is incorrect and should be replaced? What “types” are acceptable to use? Is there an easy way to determine which custom device handlers are affected?


(Brad) #15

http://docs.smartthings.com/en/latest/device-type-developers-guide/tiles-metadata.html?highlight=multi%20attribute#multi-attribute-tile-types

“lighting”, “thermostat”, “mediaPlayer”, and “generic” are the accepted types.

I don’t know of a programatically way to check unfortunately. If you have an Android device, the app shouldn’t crash but will show a “?” which would help narrow down which device handlers need updating.


#16

@Brad_ST,

What’s being done about the sorting issue?


(Neal B) #17

I found the errant device handler. Added the correct code. The app is no longer crashing, but like the other reports, I also am unable to re-arrange my devices.


(Brad) #18

The issue with sorting has been documented internally but I don’t have a timeline on a fix.


(Andreas A.) #19

I’m confused. “It has been documented” sounds like past tense to me. Was this regression known before the app was released? If so, wouldn’t it have been prudent to let people know it is broken and will return at some later date (assuming this release was important enough for some other reason to get out there now)?


(Brad) #20

Sorry for the confusion, past tense as in “I filed a bug report”. I am able to reproduce and reported the issue to our mobile developers.


#21

Regression testing does not mean you test to make sure you are going backwards …

Sorry, I couldn’t resist. I can only shake my head on this one.


(Tyrsen) #22

Same for me, once it loaded it shuts down! Tried to reinstall it but didn’t work!


(Jimmy) #23

Log into the IDE and fix your device handler as Brad posted above


(Tim) #24

For me, app doesn’t crash, but favorites and devices fail to load. Smart apps work, though. iPhone 6+ iOS 11.2.2.


#25

If I try to open any Wemo device in the SmartApp the app crashes.

Reported to Support. Ticket #500932 if anyone wishes to refer to it.

I’m on iOS.


(jkp) #26

It may also apply to your case even though you are not crashing. You should check it to see if you have the same settings.

If not, contact ST support :slight_smile:


(Mike) #27

I have a device handler that no longer is working. Well not working is not exactly correct, it still seems to be running but I can not open the device for my Aeon energy V2 monitor. I just get a screen that says something is wrong, we can’t load your screen right now. I have looked through the code and it doesn’t seem to use any multiAttributeTiles. All I see are standard and Value. Do these have issues as well?

Something else I should look at? I sent in a support request but haven’t received a reply yet. Had not seen this thread at that time.