heroku local malfunctions versus heroku cloud deployed App

[pbmorton]

I have a java Spring Boot webapp on heroku. It runs perfectly on the cloud. But when run locally it appears to use a stale resource (i.e. a resource from a previous build that was previously run using heroku local). The resource is inside my jar called nymmbl1-1.0.jar. I have 100% verified the resource is correct in target\nymmbl1-1.0.jar and ~.m2\repository\com\nymmbl\nymmbl1\1.0\nymmbl1-1.0.jar. When run locally the resource is old. It's as though heroku local is using some cached version of the resource.

Has anyone ever seen anything like this?

The out-of-date resource is a local read-only SQlite database. When running "heroku local" the database is accessed but the content returned is different than the actual database content in the current jar. The content returned is from an older version of the SQLite DB that is not in the current JAR.

As I said, this problem is not observed when run on the cloud. I've rebooted my machine, searched everywhere for answers for over 2 days, and so far found no solution.

My guess is that "heroku local" is doing something I don't expect. Can you suggest what may be the problem or how to debug this?

[pbmorton]

Closed here and opened equivalent issue at heroku/cli#612