We're getting lots of "Unhandled Exceptions" in ERA, but there's no such exception. I don't see any reason why Garmin would intentionally hide the real exception form the developers (especially that the documentation mentions some possible exceptions)
My problem is with Properties.setValue. I am pretty sure it's not any of these, or at least it shouldn't be:
- (Application.ObjectStoreAccessException) — 
Thrown if called from a background process on device that does not have ConnectIQ 3.2.0 support. Data can always be passed to the foreground process from a background process with Background.exit(). 
- (Lang.UnexpectedTypeException) — 
Thrown if key is a disallowed data type 
- (Properties.InvalidKeyException) — 
Thrown if key does not exist in Application Properties See the rest below, the stupid forum doesn't let me to post it in one piece 
 
				 
		 
				
- 
	
	
					
				  
 
		
			
											
					flocsy🤠
				
					
		
			5 months ago
		
			 
 
	
		- 
				Cancel
			
 
 
 
		 			
		- 
					
						
						
													Up
						
						0
													Down
											
				
- 
															
				
- 
				More
			
- 
				Cancel
			
 
 
 
 
Comment- 
	
	
					
				  
 
		
			
											
					flocsy🤠
				
					
		
			5 months ago
		
			 
 
	
		- 
				Cancel
			
 
 
 
		 			
		- 
					
						
						
													Up
						
						0
													Down
											
				
- 
															
				
- 
				More
			
- 
				Cancel
			
 
 
 
 
Children