PowerApps Build 2.0.791 - 2.0.795 - There was a Problem Loading Your Data

[panterra]

I have published builds of our PowerApp using 2.0.791 and 2.0.795 and started getting an error in the stock splash screen. 

This error was not present on builds relesaed with PowerApps 2.0.762.  I belive I have isolated the issue to the app's OnStart event (more details below).  

This exact code is working fine on builds published 2.0.762.  However, this code is generating errors in build 2.0.791.  When I remove this code and publish it using build 2.0.762, the error goes away.  

Has anyone seen similar issues?  Or does anyone from the community / product team have any ideas? 

I tried to republish using an older version of the studio referenced here, but am unable to open our Development environment using it. 

Clear(collSessionAudio);
LoadData(collSessionAudio, "ocollSessionAudio", true);
LoadData(collPlansMaster, "ocollPlansMaster", true);
Clear(collPreferences);
LoadData(collPreferences, "ocollPreferences", true);
If(CountRows(collPreferences) > 0, Set(searchFilterVal, LookUp(collPreferences, myFilter<>"", myFilter) ), Set(searchFilterVal, ""));

[wyotim]

Thank you all for keeping up on this issue. I developed a workaround for one of our apps, but it only stops the errors on the second time the app is run. 

After the LoadData takes place, I check if the collection is empty. If it is, I collect a single row from a similar table or the data source (or set up the table if I can't collect from anything), clear that collection, and then run SaveData on it. I posted code samples below. Clearing the collection in the second example may be superfluous, but at this point I want to know everything is being handled.

As I mentioned, it stops the errors the second time the app is run and it does add some time to the app starting, but at least the errors are handled (for now! ). 

//Example of collecting from a similar collection//

LoadData(MaintenanceRecordQueueCollection, "LocalMaintenanceRecordQueue", true);
If(IsEmpty(MaintenanceRecordQueueCollection),
    Collect(MaintenanceRecordQueueCollection, First(MaintenanceRecordCollection));
    Clear(MaintenanceRecordQueueCollection);
    SaveData(MaintenanceRecordQueueCollection, "LocalMaintenanceRecordQueue")
)

//Example of setting up collection parameters//

LoadData(EmailQueueCollection, "LocalEmailQueue", true);
If(IsEmpty(EmailQueueCollection),
	Collect(EmailQueueCollection,
    		{EmailRecipient: ""},
    		{EmailSubject: ""},
    		{EmailBody: ""},
    		{EmailImportance: ""}
	);
	Clear(EmailQueueCollection);
    SaveData(EmailQueueCollection, "LocalEmailQueue")
)

[claudiosvcc]

Hi,

I would like to understand better the issue. I'm not able to repro that locally. Is there anything special about the data you're saving or trying to load?

Can you please let me know which device are you running PowerApps?

The IgnoreNonexistentFile seems to be working properly to me too. So I'm wondering if that could be a device/platform specific issue?

If it's also possible to attach an example app it would be perfect.

[Mark1]

In my situation:

1. The data is initially being pulled from a SharePoint list (datasource) down to a local collection. 

2. The user is then making changes to the local collection

3. If the user is connected, then the changes are sent back to SharePoint using various commands (Patch, UpdateIF, RemoveIF), and SaveData is not used to create other local collections.

4. If the user is not connected, then the changed records are saved (using SaveData) to other local collections (newrecords, updatedrecord, removerecords) so that the records can be sync'd back to SharePoint when the user is online.  

In the On-Start for the app, I'm using LoadData to load all the possible local collections. 

LoadData(NewRecords, "NewRecords", true);
LoadData(UpdateRecords, "UpdateRecords", true);
LoadData(RemoveRecords, "RemoveRecords", true);
If(Connection.Connected, 
	ClearCollect(MyData, Test) ; SaveData(MyData, "MyData"),
	LoadData(MyData, "MyData", true))

Now in testing this on IOS and Android, the app works fine in my Development environment (suppresses the LoadData missing file error "There was a problem loading your data").  In my Default (production) environment, the app displays the error.

To move the file from Development to Production environments:

1. Open the app on Development

2. Save As - to my local computer's file system

3. Change to the Default (Production) environment

4. Open from my local computer's file system

5. Save the app to the cloud in the Production environment

Anyone that opens the app in production gets the error, but anyone that opens the app in Development does not see the error.

Hope that helps!

-Mark

I'm not sure if attaching the app would be useable since it is connecting to a SharePoint list (datasource) that you probably don't have access to.  Let me know if you need anything different.

[claudiosvcc]

Thanks for sharing the app. The sharepoint doesn't matter much once the problem is on LoadData, so I don't care much if the sharepoint update will fail. I can't see any failure happening on the first execution as mentioned.

I've been investigating this issue last days. We indeed had some recent changes that should fix similar problems, and indeed I'm not able to see the issue. What I believe it could be happening is a version mismatch. Do you mind sending us a screen shot of the app version history? Just go to web.powerapps.com > app details > Versions. We're suspecting your app on Dev environment has latest version while the Production don't. Even if that's not the case, it would be great for us see the exact version your're running into issue so we can verify that.

Aditionally, can you please test this: get latest studio (or web version) and publish the app again on your Prod environment? Try also using mobile 820 version.

[Mark1]

So this Test app did not exist in our Production environment before today.   I had pulled up the Test app that I created last year in the Dev environment in Studio, saved it locally, then saved it to Production (see screenshots).  This makes it version 1 in Production, and Version 52 in Development.

I'm using Powerapps Studio version 2.0.820.   I republished the app to production (moved a button, saved, published, making it now Version 2).  I refreshed on my Android, and verified that it did download the newly published version. I'm still getting the same error on my Android.  

The Android Powerapps version is 3.18032.0 (there is not a newer version in the Google Play store).  I'm not sure how to get the 820 version?

For IOS, I'm using an iPhone to test.  The version was 2.0.811.  I updated to 2.0.812.  Same error message loading data. Checked again for updates to PowerApps.  Version 3.18032.0 was now available for download.  Installed new version.  Same error message loading data.  No further updates available from Apple store.

Is there a different method that I should be using to move Dev apps to Prod?  

[claudiosvcc]

Hi,

Thanks for checking this.

We believe we have identified the issue and we're working on a fix.

[RickBr]

Hello, 

Please, any news around this issue? We a doing an App with Offline Sharepoint, as a customer pilot, and this is happening to us as well.

Thank you!

[panterra]

I saw that the PowerApps team just released the useful IfError Experimental feature: https://powerapps.microsoft.com/en-us/blog/new-feature-error-handling-and-writing-null-values-to-dat...

I tried wrapping calls like the ones that generate our error in this function, but it didn't seem to change the result. 

[Anonymous]

Hi claudiosvcc 

Could you please provide an update on this?

I am having the same issue, and it is simply not a great user experience if they are 'greeted' with an error message when loading the app. 😉

[Mark1]

Still not fixed here as well.