I currently have a service module that looks into a sqlite database for a list of queued files to upload to a cloud server. Previously I had it setup to upload files to an FTP server and up until these past few days, I can't get the service to stop after calling the "ServiceStop("")" sub like I did in the past. I did try out running the service in the foreground and once I did that, I couldn't get the foregound service to stop with a Service.Stopforeground(1) code. Then I changed it back to how it was before and now no matter what I do the service won't end. So once it'd done looping through and uploading all the necessary files and they are deleted from the phone, the call to get data from the table in the sqlite database throws an exception since there is no data to pull and the server crashes. It's like the "StopService" call is getting skipped over or ignored. It honestly doesn't make sense why it won't work now when the same code worked before.
What could cause the service not to stop even when it is told to? I even tried deleting the module, creating another one, and pasting in the previous text.
What could cause the service not to stop even when it is told to? I even tried deleting the module, creating another one, and pasting in the previous text.